Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8431da25a954dde1118ec5d7139def84ac49a9f1f19e46510e1a4d6ea08ea680

Tx prefix hash: 548f1da011fc71978433ec80c14efd8098946a17b89e5f44c058dca78503ca63
Tx public key: e59a87b4ef6cde3d6769e6715afd62b71755ea80f216b01441f0c3079c77f1d5
Timestamp: 1722080455 Timestamp [UCT]: 2024-07-27 11:40:55 Age [y:d:h:m:s]: 01:107:04:37:53
Block: 1074804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335105 RingCT/type: yes/0
Extra: 01e59a87b4ef6cde3d6769e6715afd62b71755ea80f216b01441f0c3079c77f1d5021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2da834bb9aa2afeae162ceef995471f7ee2cec8f324d5aa1a2b57293add68235 0.600000000000 1547323 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": 1074814, "vin": [ { "gen": { "height": 1074804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2da834bb9aa2afeae162ceef995471f7ee2cec8f324d5aa1a2b57293add68235" } } ], "extra": [ 1, 229, 154, 135, 180, 239, 108, 222, 61, 103, 105, 230, 113, 90, 253, 98, 183, 23, 85, 234, 128, 242, 22, 176, 20, 65, 240, 195, 7, 156, 119, 241, 213, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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