Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9852121278ddf56e9ec281f178d8d005a0658263fb65bb9496c0a8eecee7242

Tx prefix hash: 464c1459af0c3041aefe3f2d77068652a71d5e1a84846c4de209ee46fd3efa8b
Tx public key: abf92fa05b6c465de1d5154a7ce94c50cf365d6247a241cf09a3ee27e7151067
Timestamp: 1734227472 Timestamp [UCT]: 2024-12-15 01:51:12 Age [y:d:h:m:s]: 00:097:02:20:14
Block: 1175417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69161 RingCT/type: yes/0
Extra: 01abf92fa05b6c465de1d5154a7ce94c50cf365d6247a241cf09a3ee27e7151067021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3cb79b1f9e01dfa99f00456a7e0883041c23c9f7442b5169274b01d383d017f 0.600000000000 1661694 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": 1175427, "vin": [ { "gen": { "height": 1175417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3cb79b1f9e01dfa99f00456a7e0883041c23c9f7442b5169274b01d383d017f" } } ], "extra": [ 1, 171, 249, 47, 160, 91, 108, 70, 93, 225, 213, 21, 74, 124, 233, 76, 80, 207, 54, 93, 98, 71, 162, 65, 207, 9, 163, 238, 39, 231, 21, 16, 103, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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