Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234bc7362a187e51d2a259f22842675518d52638f67d33eea8e66263b8a25be7

Tx prefix hash: 636fc8f8c6958b6322b6f128a35368bdd7f60df1a480a2f6a58f32506f0ecd84
Tx public key: 4854563ff9eaa32a39dc1cc1fdd042e24fe8b050ac77a16cadf7f44f990fa28c
Timestamp: 1719437693 Timestamp [UCT]: 2024-06-26 21:34:53 Age [y:d:h:m:s]: 00:322:22:20:30
Block: 1052881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230793 RingCT/type: yes/0
Extra: 014854563ff9eaa32a39dc1cc1fdd042e24fe8b050ac77a16cadf7f44f990fa28c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 263462ebd382fb5876eaefd2795f07b113b345af99de4bc8888620c1c7beaa3e 0.600000000000 1523218 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": 1052891, "vin": [ { "gen": { "height": 1052881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "263462ebd382fb5876eaefd2795f07b113b345af99de4bc8888620c1c7beaa3e" } } ], "extra": [ 1, 72, 84, 86, 63, 249, 234, 163, 42, 57, 220, 28, 193, 253, 208, 66, 226, 79, 232, 176, 80, 172, 119, 161, 108, 173, 247, 244, 79, 153, 15, 162, 140, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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