Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0bceb9b49fb2babb8b5400110f53c9e3894171f2112f3add31b6e51fd3bc109

Tx prefix hash: f57fc9ebf0ad0405b98046504fdd41b997ad181c0e4c67f87c4a1a7a85a7de30
Tx public key: 4740ae6abbe682e15a8945669195869729b794a1fd6ad8b335ead3e93c5e27c6
Timestamp: 1701738592 Timestamp [UCT]: 2023-12-05 01:09:52 Age [y:d:h:m:s]: 01:188:05:10:41
Block: 906152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395725 RingCT/type: yes/0
Extra: 014740ae6abbe682e15a8945669195869729b794a1fd6ad8b335ead3e93c5e27c6021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.610298408000 dcy

stealth address amount amount idx
00: 77a1793656b0fec831079a6eff09c45461528653a348fa5892238de6df9455b3 0.610298408000 1363077 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": 906162, "vin": [ { "gen": { "height": 906152 } } ], "vout": [ { "amount": 610298408, "target": { "key": "77a1793656b0fec831079a6eff09c45461528653a348fa5892238de6df9455b3" } } ], "extra": [ 1, 71, 64, 174, 106, 187, 230, 130, 225, 90, 137, 69, 102, 145, 149, 134, 151, 41, 183, 148, 161, 253, 106, 216, 179, 53, 234, 211, 233, 60, 94, 39, 198, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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