Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06d531a96f0167edd94a2a8229357580b236e19b665af93b541b9415628efb4d

Tx prefix hash: f7f88f55dfe0d4facbd6945876fb50e63c714d16591a3404c0d1fa7e67a5d54f
Tx public key: 0da1f3ac29c4fd87ea8589e4b05d13f9251b88cce0e5aa87516a16b06b56f691
Timestamp: 1695506158 Timestamp [UCT]: 2023-09-23 21:55:58 Age [y:d:h:m:s]: 01:053:12:27:22
Block: 854684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299501 RingCT/type: yes/0
Extra: 010da1f3ac29c4fd87ea8589e4b05d13f9251b88cce0e5aa87516a16b06b56f6910211000000114b8f5122000000000000000000

1 output(s) for total of 0.903810040000 dcy

stealth address amount amount idx
00: 6f27d6166f9027a9ea2f87f160567c578538de2d90372fbb860ab3f47ea1952d 0.903810040000 1308670 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": 854694, "vin": [ { "gen": { "height": 854684 } } ], "vout": [ { "amount": 903810040, "target": { "key": "6f27d6166f9027a9ea2f87f160567c578538de2d90372fbb860ab3f47ea1952d" } } ], "extra": [ 1, 13, 161, 243, 172, 41, 196, 253, 135, 234, 133, 137, 228, 176, 93, 19, 249, 37, 27, 136, 204, 224, 229, 170, 135, 81, 106, 22, 176, 107, 86, 246, 145, 2, 17, 0, 0, 0, 17, 75, 143, 81, 34, 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