Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a28dc97966952c848ed7a5f93c5b3a0f18d9e94ed754a9d564558a584fef42bd

Tx prefix hash: 3f526a7ff860366c5fc818a1542a801c0b104bc347042684aab58c502dbfed9c
Tx public key: e0a1de34df9377c42eb975f78686f477651f9a6bf5e6684050626dd2bd0be8f7
Timestamp: 1730389674 Timestamp [UCT]: 2024-10-31 15:47:54 Age [y:d:h:m:s]: 00:218:19:18:53
Block: 1143612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156259 RingCT/type: yes/0
Extra: 01e0a1de34df9377c42eb975f78686f477651f9a6bf5e6684050626dd2bd0be8f7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c364bfb732bac2623baeba5deb0d14cf99b5fe99c495bd0ee2ff1b6c1a72875 0.600000000000 1627541 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": 1143622, "vin": [ { "gen": { "height": 1143612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c364bfb732bac2623baeba5deb0d14cf99b5fe99c495bd0ee2ff1b6c1a72875" } } ], "extra": [ 1, 224, 161, 222, 52, 223, 147, 119, 196, 46, 185, 117, 247, 134, 134, 244, 119, 101, 31, 154, 107, 245, 230, 104, 64, 80, 98, 109, 210, 189, 11, 232, 247, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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