Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48b5673a2091b9605b5402a2f55c8df2c244cbffba118ff902fb8c0a8db6d81

Tx prefix hash: 9589d174d5f5b4f1fa210c50aa1da1163d8b0abf96335015e85bc1461d1efedd
Tx public key: 969182f88a62318c734617d0781018975fba7345d77889ec0c6bb92ffafe9cba
Timestamp: 1726936578 Timestamp [UCT]: 2024-09-21 16:36:18 Age [y:d:h:m:s]: 00:071:00:14:28
Block: 1115059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50776 RingCT/type: yes/0
Extra: 01969182f88a62318c734617d0781018975fba7345d77889ec0c6bb92ffafe9cba02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37c27c7b52dc2c9707e6df5b5941b9f626323c210855fd6375d7d00a5e02c208 0.600000000000 1595062 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": 1115069, "vin": [ { "gen": { "height": 1115059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37c27c7b52dc2c9707e6df5b5941b9f626323c210855fd6375d7d00a5e02c208" } } ], "extra": [ 1, 150, 145, 130, 248, 138, 98, 49, 140, 115, 70, 23, 208, 120, 16, 24, 151, 95, 186, 115, 69, 215, 120, 137, 236, 12, 107, 185, 47, 250, 254, 156, 186, 2, 17, 0, 0, 0, 6, 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