Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: acaf5588b590e87deca25e0d257c623b6f256e3363c435e356dfb045ac8ea806

Tx prefix hash: 955a7e0aa44b82b14f5febf6a48a4b4e7011b0f8007d69e2a9718ecd94ce6e2a
Tx public key: ca32ff45f1fc7d7e4c858a5934eace6fed1ac47ec47e9ba4e5d777ef458c085b
Timestamp: 1582342313 Timestamp [UCT]: 2020-02-22 03:31:53 Age [y:d:h:m:s]: 05:055:18:20:56
Block: 70059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192931 RingCT/type: yes/0
Extra: 01ca32ff45f1fc7d7e4c858a5934eace6fed1ac47ec47e9ba4e5d777ef458c085b0211000000010aca7173000000000000000000

1 output(s) for total of 359.638563019000 dcy

stealth address amount amount idx
00: 6f98413b0ba6a512ae90c6ffa2d569a6044b9d64af6631e3c2336c7720f3f91c 359.638563019000 129265 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 70069, "vin": [ { "gen": { "height": 70059 } } ], "vout": [ { "amount": 359638563019, "target": { "key": "6f98413b0ba6a512ae90c6ffa2d569a6044b9d64af6631e3c2336c7720f3f91c" } } ], "extra": [ 1, 202, 50, 255, 69, 241, 252, 125, 126, 76, 133, 138, 89, 52, 234, 206, 111, 237, 26, 196, 126, 196, 126, 155, 164, 229, 215, 119, 239, 69, 140, 8, 91, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8