Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc8fe669fd91add411dc66ddf9fa26acd21c4000a1b4257466583ef45a32bf6

Tx prefix hash: 5e8aa62bf78ab17b58734ec81cad839f825cd6fe1d4870a2e48df2e0dab9bd8c
Tx public key: 8947620eb1a59fa758c1a81b239382d2fd0c3fb3108fe3e3989f96eee885e368
Timestamp: 1702905547 Timestamp [UCT]: 2023-12-18 13:19:07 Age [y:d:h:m:s]: 01:071:20:02:17
Block: 915834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312440 RingCT/type: yes/0
Extra: 018947620eb1a59fa758c1a81b239382d2fd0c3fb3108fe3e3989f96eee885e36802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4fddfd5ff379b1e6589228d03ba952ccb7baf2a1eb4af2afc580dd21c2a152 0.600000000000 1373268 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": 915844, "vin": [ { "gen": { "height": 915834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4fddfd5ff379b1e6589228d03ba952ccb7baf2a1eb4af2afc580dd21c2a152" } } ], "extra": [ 1, 137, 71, 98, 14, 177, 165, 159, 167, 88, 193, 168, 27, 35, 147, 130, 210, 253, 12, 63, 179, 16, 143, 227, 227, 152, 159, 150, 238, 232, 133, 227, 104, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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