Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3123d4e768b6708b71eed7e90b55995771bc24724849cc4cc9ec382c2b7fdcfc

Tx prefix hash: a837332c05bff4a9186aa878ae92f3fafbda27c1d06a37405b7d8bc7a7450820
Tx public key: 8bb2b05b38643e852780ac53fe982e039e96b84eed0a5141ad3f2a314e13dc86
Timestamp: 1700960826 Timestamp [UCT]: 2023-11-26 01:07:06 Age [y:d:h:m:s]: 01:348:20:42:33
Block: 899702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508222 RingCT/type: yes/0
Extra: 018bb2b05b38643e852780ac53fe982e039e96b84eed0a5141ad3f2a314e13dc8602110000000133af99f4000000000000000000

1 output(s) for total of 0.641082281000 dcy

stealth address amount amount idx
00: 2b6ac359d4250cf4493f7de53ab2dbd2d317307db74d47a227443a3eb2491b6c 0.641082281000 1356165 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": 899712, "vin": [ { "gen": { "height": 899702 } } ], "vout": [ { "amount": 641082281, "target": { "key": "2b6ac359d4250cf4493f7de53ab2dbd2d317307db74d47a227443a3eb2491b6c" } } ], "extra": [ 1, 139, 178, 176, 91, 56, 100, 62, 133, 39, 128, 172, 83, 254, 152, 46, 3, 158, 150, 184, 78, 237, 10, 81, 65, 173, 63, 42, 49, 78, 19, 220, 134, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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