Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58356ff108fdb051134d0e66fb08fa8e8fb528becfaba345b4192f6955c22611

Tx prefix hash: 77cc0ff01e1fe7e12c335491c07c30a16abd5ac88267646ff27d46324944ac1b
Tx public key: f37e7a9b8e1d9af1e3a648334d26e96d0e34976c3d8ceb7c58470dfbb1a447d8
Timestamp: 1700094911 Timestamp [UCT]: 2023-11-16 00:35:11 Age [y:d:h:m:s]: 01:154:14:05:03
Block: 892524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371684 RingCT/type: yes/0
Extra: 01f37e7a9b8e1d9af1e3a648334d26e96d0e34976c3d8ceb7c58470dfbb1a447d8021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.677169639000 dcy

stealth address amount amount idx
00: 4e5fa1f940297c52272a2a1e7a27806b3641efd7105a83f2227017396eb44635 0.677169639000 1348643 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": 892534, "vin": [ { "gen": { "height": 892524 } } ], "vout": [ { "amount": 677169639, "target": { "key": "4e5fa1f940297c52272a2a1e7a27806b3641efd7105a83f2227017396eb44635" } } ], "extra": [ 1, 243, 126, 122, 155, 142, 29, 154, 241, 227, 166, 72, 51, 77, 38, 233, 109, 14, 52, 151, 108, 61, 140, 235, 124, 88, 71, 13, 251, 177, 164, 71, 216, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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