Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8401370bb4e37d4941cd020a824009c5b93793f98ca8243c26dc9162b0bdf4d

Tx prefix hash: 268aab1c855f078ff4352f91c4ac769fb165737e68fd7b9497b4ad00f7d41d77
Tx public key: 2d39f13f07c9fc01a821bf7859d682bb6f33f7e5c400fcc6fc1d62f790332e13
Timestamp: 1701738954 Timestamp [UCT]: 2023-12-05 01:15:54 Age [y:d:h:m:s]: 01:119:01:18:54
Block: 906156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346232 RingCT/type: yes/0
Extra: 012d39f13f07c9fc01a821bf7859d682bb6f33f7e5c400fcc6fc1d62f790332e1302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.610279783000 dcy

stealth address amount amount idx
00: 801ffbb9b35311baee789b6dac2585b6b28d62eba5f75635b28c434648ca279f 0.610279783000 1363081 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": 906166, "vin": [ { "gen": { "height": 906156 } } ], "vout": [ { "amount": 610279783, "target": { "key": "801ffbb9b35311baee789b6dac2585b6b28d62eba5f75635b28c434648ca279f" } } ], "extra": [ 1, 45, 57, 241, 63, 7, 201, 252, 1, 168, 33, 191, 120, 89, 214, 130, 187, 111, 51, 247, 229, 196, 0, 252, 198, 252, 29, 98, 247, 144, 51, 46, 19, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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