Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f68157376a161eed4141074ce531069fcf989c6deeb68304e91da82eb4284e

Tx prefix hash: 8c8eb2bbb14fdfc471cb584d033aa70d0f3f7e912462e2842c48837ae1464e30
Tx public key: bf3a589c3b2ab71ee833dc4da075fef5dd01a8f848add172a9830067c1604d58
Timestamp: 1641331386 Timestamp [UCT]: 2022-01-04 21:23:06 Age [y:d:h:m:s]: 03:113:06:09:52
Block: 410431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 859881 RingCT/type: yes/0
Extra: 01bf3a589c3b2ab71ee833dc4da075fef5dd01a8f848add172a9830067c1604d58021100000009cda45b65000000000000000000

1 output(s) for total of 26.796128707000 dcy

stealth address amount amount idx
00: 288349adbdb429ebbc11007646fdc56fb9fd3ebc686a038c7fb77186054d5cf6 26.796128707000 813421 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": 410441, "vin": [ { "gen": { "height": 410431 } } ], "vout": [ { "amount": 26796128707, "target": { "key": "288349adbdb429ebbc11007646fdc56fb9fd3ebc686a038c7fb77186054d5cf6" } } ], "extra": [ 1, 191, 58, 88, 156, 59, 42, 183, 30, 232, 51, 220, 77, 160, 117, 254, 245, 221, 1, 168, 248, 72, 173, 209, 114, 169, 131, 0, 103, 193, 96, 77, 88, 2, 17, 0, 0, 0, 9, 205, 164, 91, 101, 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