Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 506415683232471f5b7f98ec6736cbe488911b0731407512025ff0e713f3cd5c

Tx prefix hash: 105703c233b74a8c146eb9fd17247aaa0e8e98fd8969dc6260f73643a3b9045d
Tx public key: 492b879b0a57e2f28347a4919842b17df64f32c5a4fbb4a4a65c96bb033c868e
Timestamp: 1649656559 Timestamp [UCT]: 2022-04-11 05:55:59 Age [y:d:h:m:s]: 02:219:02:37:08
Block: 477779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676346 RingCT/type: yes/0
Extra: 01492b879b0a57e2f28347a4919842b17df64f32c5a4fbb4a4a65c96bb033c868e021100000001c9067537000000000000000000

1 output(s) for total of 16.029503681000 dcy

stealth address amount amount idx
00: f5d4e36d230cbe6dd4efb2351df5e96d710d089724514e0ab1427319927f5de1 16.029503681000 898472 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": 477789, "vin": [ { "gen": { "height": 477779 } } ], "vout": [ { "amount": 16029503681, "target": { "key": "f5d4e36d230cbe6dd4efb2351df5e96d710d089724514e0ab1427319927f5de1" } } ], "extra": [ 1, 73, 43, 135, 155, 10, 87, 226, 242, 131, 71, 164, 145, 152, 66, 177, 125, 246, 79, 50, 197, 164, 251, 180, 164, 166, 92, 150, 187, 3, 60, 134, 142, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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