Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c7d8f3fc2f31f4e5335b9168b40116484c5c4253d8cca1a91c8ba01491fe13

Tx prefix hash: 686e75a0863ad29431c0138abb4b276680b9132fbdd95917abc2638acf1b6233
Tx public key: b6cad5bb1e57b1bb836a0762128faf282f3d76c30b1fa4d91abaeff4b9fadf45
Timestamp: 1731943485 Timestamp [UCT]: 2024-11-18 15:24:45 Age [y:d:h:m:s]: 01:067:18:14:23
Block: 1156469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306758 RingCT/type: yes/0
Extra: 01b6cad5bb1e57b1bb836a0762128faf282f3d76c30b1fa4d91abaeff4b9fadf45021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf2a551ce24898d56859c4eb7e74e511c61f7d102c0cf6bfb02e60fdd03e6727 0.600000000000 1642092 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": 1156479, "vin": [ { "gen": { "height": 1156469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf2a551ce24898d56859c4eb7e74e511c61f7d102c0cf6bfb02e60fdd03e6727" } } ], "extra": [ 1, 182, 202, 213, 187, 30, 87, 177, 187, 131, 106, 7, 98, 18, 143, 175, 40, 47, 61, 118, 195, 11, 31, 164, 217, 26, 186, 239, 244, 185, 250, 223, 69, 2, 17, 0, 0, 0, 4, 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