Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6108be44e022860643ea5d90ab7d1ce894691b44146807624f73d462685de2a1

Tx prefix hash: ed0cf94a3f0b10c594488e1c8e0e9ef6eeb80ea28fd6c5b96bdf6b0514912501
Tx public key: 36c4a021f3a4dc8211b770f64277b7ee9c51b6e141183546f7d7b4e8c7a7d6ef
Timestamp: 1721380118 Timestamp [UCT]: 2024-07-19 09:08:38 Age [y:d:h:m:s]: 00:332:02:15:25
Block: 1069012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237195 RingCT/type: yes/0
Extra: 0136c4a021f3a4dc8211b770f64277b7ee9c51b6e141183546f7d7b4e8c7a7d6ef021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3214046bdf9f7f0b11cf714f0e2eb0da586db24e633c025672e4ecef18311ad 0.600000000000 1540267 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": 1069022, "vin": [ { "gen": { "height": 1069012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3214046bdf9f7f0b11cf714f0e2eb0da586db24e633c025672e4ecef18311ad" } } ], "extra": [ 1, 54, 196, 160, 33, 243, 164, 220, 130, 17, 183, 112, 246, 66, 119, 183, 238, 156, 81, 182, 225, 65, 24, 53, 70, 247, 215, 180, 232, 199, 167, 214, 239, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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