Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2da4238946934a41380dd74ba866a8ac845ca5b1e9e401ccedfb7d979920ba7

Tx prefix hash: c233ce986d923706ae0d9df870fb411f07d10aed81959ab5a08c9ad83f771ce9
Tx public key: c39d4bbc6dd68b47cb8d57e8ac768134e51c34fa3d0bde3fa58dedcdd88a9d1b
Timestamp: 1677915740 Timestamp [UCT]: 2023-03-04 07:42:20 Age [y:d:h:m:s]: 02:031:18:30:22
Block: 709543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544265 RingCT/type: yes/0
Extra: 01c39d4bbc6dd68b47cb8d57e8ac768134e51c34fa3d0bde3fa58dedcdd88a9d1b0211000000075029cbac000000000000000000

1 output(s) for total of 2.735201935000 dcy

stealth address amount amount idx
00: 5402686664d8880b1648bca8a898dc7812cf6cba1b319254e3137f114435b304 2.735201935000 1153534 of 0

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": 709553, "vin": [ { "gen": { "height": 709543 } } ], "vout": [ { "amount": 2735201935, "target": { "key": "5402686664d8880b1648bca8a898dc7812cf6cba1b319254e3137f114435b304" } } ], "extra": [ 1, 195, 157, 75, 188, 109, 214, 139, 71, 203, 141, 87, 232, 172, 118, 129, 52, 229, 28, 52, 250, 61, 11, 222, 63, 165, 141, 237, 205, 216, 138, 157, 27, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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