Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6117f87e4f422fbed70675d95ce74facfe1558acac43d2e90b934ad72c64e48d

Tx prefix hash: 77b79499c718d6acf08a0ecc416c5e651fb4c4df2ff9e41bd966edefe00ccf3d
Tx public key: 1ed4c16423e2afb087e28daf74349106c21e5260c887b18ab0a66415e06f6aee
Timestamp: 1711339020 Timestamp [UCT]: 2024-03-25 03:57:00 Age [y:d:h:m:s]: 01:059:00:10:28
Block: 985771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303165 RingCT/type: yes/0
Extra: 011ed4c16423e2afb087e28daf74349106c21e5260c887b18ab0a66415e06f6aee02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64ba7bbc4dd90ce58a497026258a0b62841bbfd8f0a42e57f64e44e95e7ce2a2 0.600000000000 1445988 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": 985781, "vin": [ { "gen": { "height": 985771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64ba7bbc4dd90ce58a497026258a0b62841bbfd8f0a42e57f64e44e95e7ce2a2" } } ], "extra": [ 1, 30, 212, 193, 100, 35, 226, 175, 176, 135, 226, 141, 175, 116, 52, 145, 6, 194, 30, 82, 96, 200, 135, 177, 138, 176, 166, 100, 21, 224, 111, 106, 238, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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