Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35030c1bb4a698f150cea6ea62d93f2e8b80c250b530f5537cfb2919c5d54719

Tx prefix hash: f23af75b0841b98d4a8df246b50c9d09b87c967d411005e5071152125443a7d0
Tx public key: 3b2cbffafa6b2a236e5945935ff697a2d0282a6baceb0b4224c289849c56e825
Timestamp: 1709670594 Timestamp [UCT]: 2024-03-05 20:29:54 Age [y:d:h:m:s]: 01:103:11:10:21
Block: 971928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334875 RingCT/type: yes/0
Extra: 013b2cbffafa6b2a236e5945935ff697a2d0282a6baceb0b4224c289849c56e8250211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85e3f55ad4391ac7ad3908196df35655a9a99972c535c1640fa1d69bfb5c9f2f 0.600000000000 1431833 of 15

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": 971938, "vin": [ { "gen": { "height": 971928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85e3f55ad4391ac7ad3908196df35655a9a99972c535c1640fa1d69bfb5c9f2f" } } ], "extra": [ 1, 59, 44, 191, 250, 250, 107, 42, 35, 110, 89, 69, 147, 95, 246, 151, 162, 208, 40, 42, 107, 172, 235, 11, 66, 36, 194, 137, 132, 156, 86, 232, 37, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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