Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4146c114abe11fbb6d074cec5826eef719a4ef04214b73a8cd83559940e883d

Tx prefix hash: f253c95d24d9f5c029fcb3ef787d2d07a823cf75ec8ecba8f75c29e09aeb0f00
Tx public key: ef184501371126cae59b94ba3fa2b46b96105c681c62064a5bccc10c2befc90e
Timestamp: 1634505591 Timestamp [UCT]: 2021-10-17 21:19:51 Age [y:d:h:m:s]: 03:071:22:31:45
Block: 355152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 829363 RingCT/type: yes/0
Extra: 01ef184501371126cae59b94ba3fa2b46b96105c681c62064a5bccc10c2befc90e02110000000b3fc41461000000000000000000

1 output(s) for total of 40.853983526000 dcy

stealth address amount amount idx
00: 09cb0843a576f747163886e5958a4fffeb2d8e5db520941907c93bf4943ae812 40.853983526000 725196 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": 355162, "vin": [ { "gen": { "height": 355152 } } ], "vout": [ { "amount": 40853983526, "target": { "key": "09cb0843a576f747163886e5958a4fffeb2d8e5db520941907c93bf4943ae812" } } ], "extra": [ 1, 239, 24, 69, 1, 55, 17, 38, 202, 229, 155, 148, 186, 63, 162, 180, 107, 150, 16, 92, 104, 28, 98, 6, 74, 91, 204, 193, 12, 43, 239, 201, 14, 2, 17, 0, 0, 0, 11, 63, 196, 20, 97, 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