Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99128ab0c654759b57baa592ed3d2bb39f66b52ec38f8d572070c03869583517

Tx prefix hash: 14b42e66f274bf4c2a22ca3db4ae6b9b6d3b3a6f540661916af39ebd6462bee3
Tx public key: 746bcd264266ef401d04b991bab012958b4df353582c6cbe38fe910ad62054fa
Timestamp: 1724684825 Timestamp [UCT]: 2024-08-26 15:07:05 Age [y:d:h:m:s]: 00:220:05:59:03
Block: 1096390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157268 RingCT/type: yes/0
Extra: 01746bcd264266ef401d04b991bab012958b4df353582c6cbe38fe910ad62054fa021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fea8cdb1b67308e0b5f8e77045c927f3f7c14a9ebbb3eee70197b4fb3620272 0.600000000000 1571579 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": 1096400, "vin": [ { "gen": { "height": 1096390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fea8cdb1b67308e0b5f8e77045c927f3f7c14a9ebbb3eee70197b4fb3620272" } } ], "extra": [ 1, 116, 107, 205, 38, 66, 102, 239, 64, 29, 4, 185, 145, 186, 176, 18, 149, 139, 77, 243, 83, 88, 44, 108, 190, 56, 254, 145, 10, 214, 32, 84, 250, 2, 17, 0, 0, 0, 2, 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