Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4384969fb3d0733eaa2958b741b5248fd087925cae7167f921000d21190d4a6

Tx prefix hash: 9ee7eeecf944d081a54c8c6a0cc24a1474ef82fbf0cccf13eb60ed7c58e72a6f
Tx public key: bfef312ee7dc9fd9efc94da418a4df675ac5e70ed8aedcac2b225b85ec8f1215
Timestamp: 1735905368 Timestamp [UCT]: 2025-01-03 11:56:08 Age [y:d:h:m:s]: 00:353:14:05:09
Block: 1189313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250245 RingCT/type: yes/0
Extra: 01bfef312ee7dc9fd9efc94da418a4df675ac5e70ed8aedcac2b225b85ec8f121502110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0523bc05dbbf79a28b2507501cb21ae5b41653a204969bc392e025d8eb37ae7 0.600000000000 1675820 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": 1189323, "vin": [ { "gen": { "height": 1189313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0523bc05dbbf79a28b2507501cb21ae5b41653a204969bc392e025d8eb37ae7" } } ], "extra": [ 1, 191, 239, 49, 46, 231, 220, 159, 217, 239, 201, 77, 164, 24, 164, 223, 103, 90, 197, 231, 14, 216, 174, 220, 172, 43, 34, 91, 133, 236, 143, 18, 21, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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