Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a052b52b6a6cc6bf6c08d08d8d9c6ce727ba9f8cf98f450463ba3841949f7f29

Tx prefix hash: ed0535eecf6d3154123a7f38c2d7071656860059ff18edc6525d910f5f6a38b4
Tx public key: b75088c02b2b03994a37035b8570fad9bf4f2668c5cbe5df62b81c43aaf36995
Timestamp: 1672876116 Timestamp [UCT]: 2023-01-04 23:48:36 Age [y:d:h:m:s]: 01:332:14:48:41
Block: 667734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498749 RingCT/type: yes/0
Extra: 01b75088c02b2b03994a37035b8570fad9bf4f2668c5cbe5df62b81c43aaf3699502110000000252542ceb000000000000000000

1 output(s) for total of 3.762877057000 dcy

stealth address amount amount idx
00: 063e0d4a482cdf67a7aa561d3722790d77fe03bcb258b066077d6ecb00bb5661 3.762877057000 1108949 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": 667744, "vin": [ { "gen": { "height": 667734 } } ], "vout": [ { "amount": 3762877057, "target": { "key": "063e0d4a482cdf67a7aa561d3722790d77fe03bcb258b066077d6ecb00bb5661" } } ], "extra": [ 1, 183, 80, 136, 192, 43, 43, 3, 153, 74, 55, 3, 91, 133, 112, 250, 217, 191, 79, 38, 104, 197, 203, 229, 223, 98, 184, 28, 67, 170, 243, 105, 149, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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