Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc281e17ae7839cca9edec04f8aa229cf90759a6e48d3ce6be2d34467f57f415

Tx prefix hash: 2446a16e0b40741cab082f26676b5d1b941856c2e375bd0faccefdae349d954f
Tx public key: 15acb6de324028d8ea9856d8801de7767bb71fb6acf641dc66cbdd774aac5894
Timestamp: 1706687816 Timestamp [UCT]: 2024-01-31 07:56:56 Age [y:d:h:m:s]: 01:364:21:31:29
Block: 947171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519517 RingCT/type: yes/0
Extra: 0115acb6de324028d8ea9856d8801de7767bb71fb6acf641dc66cbdd774aac589402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e88221833c112a2aec856b4c989c15306766d1d878c55b74e2f10f8bc451b5e 0.600000000000 1405519 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": 947181, "vin": [ { "gen": { "height": 947171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e88221833c112a2aec856b4c989c15306766d1d878c55b74e2f10f8bc451b5e" } } ], "extra": [ 1, 21, 172, 182, 222, 50, 64, 40, 216, 234, 152, 86, 216, 128, 29, 231, 118, 123, 183, 31, 182, 172, 246, 65, 220, 102, 203, 221, 119, 74, 172, 88, 148, 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