Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e56d2676078ec99b97bc291450e0e684e0cc2dfb9d73f85e7f1071a36257695

Tx prefix hash: 37bc9e318d6aae8007dc3b189c9ee055cbf2fdc0cc4e9d5fd1fc3ff025a0bdde
Tx public key: ff41581ea44966e1c480cc18be90f6996bb9569a4038d37b12e31033f19d13b7
Timestamp: 1747653542 Timestamp [UCT]: 2025-05-19 11:19:02 Age [y:d:h:m:s]: 00:142:16:18:14
Block: 1286280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99623 RingCT/type: yes/0
Extra: 01ff41581ea44966e1c480cc18be90f6996bb9569a4038d37b12e31033f19d13b70211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcf6533bb8c9aa56e1d7d3d7e99059d1a7703a015474af645b94b52b4dafaad4 0.600000000000 1773745 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": 1286290, "vin": [ { "gen": { "height": 1286280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcf6533bb8c9aa56e1d7d3d7e99059d1a7703a015474af645b94b52b4dafaad4" } } ], "extra": [ 1, 255, 65, 88, 30, 164, 73, 102, 225, 196, 128, 204, 24, 190, 144, 246, 153, 107, 185, 86, 154, 64, 56, 211, 123, 18, 227, 16, 51, 241, 157, 19, 183, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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