Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57e002551eae35366644bb61be141a3a0ca7e7e7970610d41bc883335929cd57

Tx prefix hash: 9c20388927a1f6755c0e80c412eb39bd71cff8bf694d1c873c008830705831be
Tx public key: 736ee4a9695b7e6393daa02eb49b7cbae16e7a7b87a36c9ddcb9f89cc3aa2364
Timestamp: 1733004490 Timestamp [UCT]: 2024-11-30 22:08:10 Age [y:d:h:m:s]: 00:114:02:25:54
Block: 1165270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81337 RingCT/type: yes/0
Extra: 01736ee4a9695b7e6393daa02eb49b7cbae16e7a7b87a36c9ddcb9f89cc3aa23640211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 568429d641754854b99a1c1d46cac173c0974ea04b8ea245519db6c35484c777 0.600000000000 1650945 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": 1165280, "vin": [ { "gen": { "height": 1165270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "568429d641754854b99a1c1d46cac173c0974ea04b8ea245519db6c35484c777" } } ], "extra": [ 1, 115, 110, 228, 169, 105, 91, 126, 99, 147, 218, 160, 46, 180, 155, 124, 186, 225, 110, 122, 123, 135, 163, 108, 157, 220, 185, 248, 156, 195, 170, 35, 100, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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