Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02232be4d04dc2a2c57dfe99ed1af54f3e58ee50a84f236c57574757dccebb91

Tx prefix hash: c9d03ad7cf9c1f7c47299a04401c8e0c0163716a8c51b87a3da6343525b02427
Tx public key: a58296728adf27c02e3f00fa6b1d32ec5cd3d009000cc538f9fd2cedde7524c5
Timestamp: 1724643788 Timestamp [UCT]: 2024-08-26 03:43:08 Age [y:d:h:m:s]: 00:227:08:58:20
Block: 1096050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162372 RingCT/type: yes/0
Extra: 01a58296728adf27c02e3f00fa6b1d32ec5cd3d009000cc538f9fd2cedde7524c5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b4d8d2b2c10785a06a4f85a7dffd975420f2eb724baf60fcc86daf3ec14aef6 0.600000000000 1571237 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": 1096060, "vin": [ { "gen": { "height": 1096050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b4d8d2b2c10785a06a4f85a7dffd975420f2eb724baf60fcc86daf3ec14aef6" } } ], "extra": [ 1, 165, 130, 150, 114, 138, 223, 39, 192, 46, 63, 0, 250, 107, 29, 50, 236, 92, 211, 208, 9, 0, 12, 197, 56, 249, 253, 44, 237, 222, 117, 36, 197, 2, 17, 0, 0, 0, 1, 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