Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3c0f2cdb72faabcf1fdd37050dbce0dd41b4222fd31982ce587d5c18ea7bd9c

Tx prefix hash: e853fcf92e03a4cd53e9d811e14fd784749fc5ed3f842d8529f5169de275aee7
Tx public key: 8b661936f71e30969c39c464dcbb1e2b6572b721c48dc5146844aea0a2a4b628
Timestamp: 1737309918 Timestamp [UCT]: 2025-01-19 18:05:18 Age [y:d:h:m:s]: 00:056:17:23:03
Block: 1200879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40368 RingCT/type: yes/0
Extra: 018b661936f71e30969c39c464dcbb1e2b6572b721c48dc5146844aea0a2a4b628021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8d80586b4e4f8e3d712b8b33c45c3efb6e268d72a2eaa42ce9b4b6df6b28f81 0.600000000000 1687526 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": 1200889, "vin": [ { "gen": { "height": 1200879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8d80586b4e4f8e3d712b8b33c45c3efb6e268d72a2eaa42ce9b4b6df6b28f81" } } ], "extra": [ 1, 139, 102, 25, 54, 247, 30, 48, 150, 156, 57, 196, 100, 220, 187, 30, 43, 101, 114, 183, 33, 196, 141, 197, 20, 104, 68, 174, 160, 162, 164, 182, 40, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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