Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6ca5866a52f525abc0ef64301cf3e11a31f6186db9dc4fbe900b368c89988c9

Tx prefix hash: 71143e5e54e3d4cf771d6c3f3667747755a20b08ea02e18097895c15604782e1
Tx public key: cdb5c83b0ee9ec949b130819a16f67864898691de0f64c3d2a0ea0a228d0c0d3
Timestamp: 1715941778 Timestamp [UCT]: 2024-05-17 10:29:38 Age [y:d:h:m:s]: 00:327:19:42:59
Block: 1023911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234320 RingCT/type: yes/0
Extra: 01cdb5c83b0ee9ec949b130819a16f67864898691de0f64c3d2a0ea0a228d0c0d302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02eab0baf2e45eb4bd8ba2bc38f15ed07161f555fd82d8f0b45a7873cd838212 0.600000000000 1489246 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": 1023921, "vin": [ { "gen": { "height": 1023911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02eab0baf2e45eb4bd8ba2bc38f15ed07161f555fd82d8f0b45a7873cd838212" } } ], "extra": [ 1, 205, 181, 200, 59, 14, 233, 236, 148, 155, 19, 8, 25, 161, 111, 103, 134, 72, 152, 105, 29, 224, 246, 76, 61, 42, 14, 160, 162, 40, 208, 192, 211, 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