Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603f1cc2586df47e8dead0e91a277d749a1ec53512f2c7038f28f31fa8cbee91

Tx prefix hash: d33e1924681c0958a4ea3a9fffefdb125a93ec47bc14f8015fbb8337880d2dee
Tx public key: 6e9af9e0d9aed1b6d01a244ec05ea60b81d49889a6b98a28c1694902823fc6ea
Timestamp: 1580880289 Timestamp [UCT]: 2020-02-05 05:24:49 Age [y:d:h:m:s]: 04:328:05:57:30
Block: 58709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126268 RingCT/type: yes/0
Extra: 016e9af9e0d9aed1b6d01a244ec05ea60b81d49889a6b98a28c1694902823fc6ea0211000000058a2ee0d9000000000000000000

1 output(s) for total of 392.169244881000 dcy

stealth address amount amount idx
00: 8a6e8a572d420a309ff7c7659cf348f3e8388eaac843463153967b4ca237df9d 392.169244881000 108533 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": 58719, "vin": [ { "gen": { "height": 58709 } } ], "vout": [ { "amount": 392169244881, "target": { "key": "8a6e8a572d420a309ff7c7659cf348f3e8388eaac843463153967b4ca237df9d" } } ], "extra": [ 1, 110, 154, 249, 224, 217, 174, 209, 182, 208, 26, 36, 78, 192, 94, 166, 11, 129, 212, 152, 137, 166, 185, 138, 40, 193, 105, 73, 2, 130, 63, 198, 234, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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