Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 596bdf0b49af77cebb299fd317e8fddd1f4a608ba611cea54229eb8f8bf7ceab

Tx prefix hash: 55f5bf4871cf15a16ae955d69fcd0763c8cd84c0df5232f184b3eb76bd36c1ac
Tx public key: c9b852f0b92ce15dd868007dabe2060da1168eb571c54ae5cfafa54e8196e0ee
Timestamp: 1704580052 Timestamp [UCT]: 2024-01-06 22:27:32 Age [y:d:h:m:s]: 01:081:23:14:39
Block: 929692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319695 RingCT/type: yes/0
Extra: 01c9b852f0b92ce15dd868007dabe2060da1168eb571c54ae5cfafa54e8196e0ee02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ef87b3e47c756d9e562c064392d7ed2da0b8ac01c7adf4a90f411d35ae9b962 0.600000000000 1387568 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": 929702, "vin": [ { "gen": { "height": 929692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ef87b3e47c756d9e562c064392d7ed2da0b8ac01c7adf4a90f411d35ae9b962" } } ], "extra": [ 1, 201, 184, 82, 240, 185, 44, 225, 93, 216, 104, 0, 125, 171, 226, 6, 13, 161, 22, 142, 181, 113, 197, 74, 229, 207, 175, 165, 78, 129, 150, 224, 238, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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