Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffae05ca28221e496cc9754394d8e40fd9e6aa431d2175af8023c8d19cd48e42

Tx prefix hash: 54d777d21944e295f09aba7c80f0e5d2e296021c8f2ff7cf03a00f85d80f3983
Tx public key: 64741af88b8fa4216ef82b84a863791f0567ddc4d25e2159274a5b012004e203
Timestamp: 1583538129 Timestamp [UCT]: 2020-03-06 23:42:09 Age [y:d:h:m:s]: 05:243:08:26:58
Block: 77870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1326792 RingCT/type: yes/0
Extra: 0164741af88b8fa4216ef82b84a863791f0567ddc4d25e2159274a5b012004e203021100000017d76d46ee000000000000000000

1 output(s) for total of 338.832576109000 dcy

stealth address amount amount idx
00: f06a261d2fcdba0cafe0e53f947a5e76b6cae3255c42d86a5fe69489397c0ae6 338.832576109000 143099 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": 77880, "vin": [ { "gen": { "height": 77870 } } ], "vout": [ { "amount": 338832576109, "target": { "key": "f06a261d2fcdba0cafe0e53f947a5e76b6cae3255c42d86a5fe69489397c0ae6" } } ], "extra": [ 1, 100, 116, 26, 248, 139, 143, 164, 33, 110, 248, 43, 132, 168, 99, 121, 31, 5, 103, 221, 196, 210, 94, 33, 89, 39, 74, 91, 1, 32, 4, 226, 3, 2, 17, 0, 0, 0, 23, 215, 109, 70, 238, 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