Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dccaa6a57e7a9f8715f1708e07f2bd603aeb23a3c17905c4a342fb6d295ed930

Tx prefix hash: 7bc8ecdc993438ecd33449beaccdf49dff97f63cc2f1c9a213b199ae69ebdd7f
Tx public key: 9bf97d5bdeb714c7f91051a3412fc818ab79b6e771dc07a4708783bde5835360
Timestamp: 1728856279 Timestamp [UCT]: 2024-10-13 21:51:19 Age [y:d:h:m:s]: 00:177:10:33:54
Block: 1130977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126602 RingCT/type: yes/0
Extra: 019bf97d5bdeb714c7f91051a3412fc818ab79b6e771dc07a4708783bde583536002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df69352d48a11936f6a1a42793b0b6333f7fbad50133d8b564871a386db4714c 0.600000000000 1613858 of 15

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": 1130987, "vin": [ { "gen": { "height": 1130977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df69352d48a11936f6a1a42793b0b6333f7fbad50133d8b564871a386db4714c" } } ], "extra": [ 1, 155, 249, 125, 91, 222, 183, 20, 199, 249, 16, 81, 163, 65, 47, 200, 24, 171, 121, 182, 231, 113, 220, 7, 164, 112, 135, 131, 189, 229, 131, 83, 96, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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