Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3812b0300c7c93412b3ca1becd048f72a602651f1979041260460c189d6b9b3

Tx prefix hash: cb29de1b0e0826bbb0675831cc6d8b655f09ccc34de70189f6a79434607e24e3
Tx public key: e922a300e5221462e451311af067c8bcaece6ee35b6822d72b4de56d698ee3d7
Timestamp: 1698413243 Timestamp [UCT]: 2023-10-27 13:27:23 Age [y:d:h:m:s]: 01:085:21:46:31
Block: 878805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322571 RingCT/type: yes/0
Extra: 01e922a300e5221462e451311af067c8bcaece6ee35b6822d72b4de56d698ee3d70211000000024b8f5122000000000000000000

1 output(s) for total of 0.751889881000 dcy

stealth address amount amount idx
00: 4418d76bfc52f295ec670bc8debc55e994b2fd246a3a26b68b9d123eda0ff893 0.751889881000 1334287 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": 878815, "vin": [ { "gen": { "height": 878805 } } ], "vout": [ { "amount": 751889881, "target": { "key": "4418d76bfc52f295ec670bc8debc55e994b2fd246a3a26b68b9d123eda0ff893" } } ], "extra": [ 1, 233, 34, 163, 0, 229, 34, 20, 98, 228, 81, 49, 26, 240, 103, 200, 188, 174, 206, 110, 227, 91, 104, 34, 215, 43, 77, 229, 109, 105, 142, 227, 215, 2, 17, 0, 0, 0, 2, 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