Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5f1908563a297ffd643734c6f96fcb3574ce3185e3390d3a366d00a914c1ed1

Tx prefix hash: aaf5fddcad1eb414a706e9b9ea9d0486a232de34c1a7029d022d5e2b319ddab9
Tx public key: ffda0e04f3cecfd8416ae032ac19b78bacfebfe95aaaf4af9544a730e71fe438
Timestamp: 1659062014 Timestamp [UCT]: 2022-07-29 02:33:34 Age [y:d:h:m:s]: 02:291:06:55:27
Block: 553965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 729397 RingCT/type: yes/0
Extra: 01ffda0e04f3cecfd8416ae032ac19b78bacfebfe95aaaf4af9544a730e71fe43802110000000bf7dd2130000000000000000000

1 output(s) for total of 8.963634091000 dcy

stealth address amount amount idx
00: a5b7e205ef6715f01068995ca1ca9ea775bf423ee6efddeb320d964eeb41afed 8.963634091000 985795 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": 553975, "vin": [ { "gen": { "height": 553965 } } ], "vout": [ { "amount": 8963634091, "target": { "key": "a5b7e205ef6715f01068995ca1ca9ea775bf423ee6efddeb320d964eeb41afed" } } ], "extra": [ 1, 255, 218, 14, 4, 243, 206, 207, 216, 65, 106, 224, 50, 172, 25, 183, 139, 172, 254, 191, 233, 90, 170, 244, 175, 149, 68, 167, 48, 231, 31, 228, 56, 2, 17, 0, 0, 0, 11, 247, 221, 33, 48, 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