Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec3cf4ba72527274f83c61a053cc47292cf3399b0bf701cec8c223adc38489a9

Tx prefix hash: 0d6b94d83a3b198ff8e3fe7f017eff0e8c98257cbf37eab76571c22e57ffb58b
Tx public key: a1d83e64433f8fa376fa5e2cc5a701948459b478e021a59c282d004988d7a1e6
Timestamp: 1726859822 Timestamp [UCT]: 2024-09-20 19:17:02 Age [y:d:h:m:s]: 00:054:14:45:11
Block: 1114428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39028 RingCT/type: yes/0
Extra: 01a1d83e64433f8fa376fa5e2cc5a701948459b478e021a59c282d004988d7a1e602110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 340ea0b0782024f527cceafe2826808039d54181738feb0b717dd56a0f8611c1 0.600000000000 1594229 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": 1114438, "vin": [ { "gen": { "height": 1114428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "340ea0b0782024f527cceafe2826808039d54181738feb0b717dd56a0f8611c1" } } ], "extra": [ 1, 161, 216, 62, 100, 67, 63, 143, 163, 118, 250, 94, 44, 197, 167, 1, 148, 132, 89, 180, 120, 224, 33, 165, 156, 40, 45, 0, 73, 136, 215, 161, 230, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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