Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ff1e93bdefa2fb0ce4ee2b252e44d8f2e80f04f243858d4248ba501e85f4b1

Tx prefix hash: 338175e27c2ddc0d9d7f69d156b668761b05d979257301dc5a2baaddcd739558
Tx public key: 10507ee626d49c3b7d0a4811aff99af05706efbf8eb964392ea0cd0b28423c6f
Timestamp: 1707729437 Timestamp [UCT]: 2024-02-12 09:17:17 Age [y:d:h:m:s]: 00:314:18:59:07
Block: 955822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225400 RingCT/type: yes/0
Extra: 0110507ee626d49c3b7d0a4811aff99af05706efbf8eb964392ea0cd0b28423c6f021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 350cc050220b641cedcc094d35dd06b753f2dbf1df3824985b311e8c73a800f9 0.600000000000 1415122 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": 955832, "vin": [ { "gen": { "height": 955822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "350cc050220b641cedcc094d35dd06b753f2dbf1df3824985b311e8c73a800f9" } } ], "extra": [ 1, 16, 80, 126, 230, 38, 212, 156, 59, 125, 10, 72, 17, 175, 249, 154, 240, 87, 6, 239, 191, 142, 185, 100, 57, 46, 160, 205, 11, 40, 66, 60, 111, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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