Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d35b0a46b11776cd5917f6969ff6fb61ec65a99230d0866d81e501357ac5c106

Tx prefix hash: f12b0be6b5df2efbc3b7eb39700f932aff2bce184f084394b058fc04dabdb018
Tx public key: e9997adde912372cd962fd7cc399381d98d6cbe93e3e1f30d6e8cee05a3dc7c6
Timestamp: 1612734361 Timestamp [UCT]: 2021-02-07 21:46:01 Age [y:d:h:m:s]: 03:293:02:37:36
Block: 194086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 968393 RingCT/type: yes/0
Extra: 01e9997adde912372cd962fd7cc399381d98d6cbe93e3e1f30d6e8cee05a3dc7c602110000002090ce5c0f000000000000000000

1 output(s) for total of 139.608912660000 dcy

stealth address amount amount idx
00: d99f5ce20ebc60ad59b8a227d7dfdc7887afb74c3eebb8e66adaf745470fa714 139.608912660000 393536 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": 194096, "vin": [ { "gen": { "height": 194086 } } ], "vout": [ { "amount": 139608912660, "target": { "key": "d99f5ce20ebc60ad59b8a227d7dfdc7887afb74c3eebb8e66adaf745470fa714" } } ], "extra": [ 1, 233, 153, 122, 221, 233, 18, 55, 44, 217, 98, 253, 124, 195, 153, 56, 29, 152, 214, 203, 233, 62, 62, 31, 48, 214, 232, 206, 224, 90, 61, 199, 198, 2, 17, 0, 0, 0, 32, 144, 206, 92, 15, 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