Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef39cf3c7e6b2f2f0d4f3d7501f792189de8d1be8d45c684457dd19510826368

Tx prefix hash: 576a80a67993da349a0dcd52dcd452ea671d756d1713b12dd2dc7a6fee9a16c7
Tx public key: 49d5317f076bcedf577627963342d2b1f5ee5b7741619ea46fa575cc7f5e197b
Timestamp: 1672806397 Timestamp [UCT]: 2023-01-04 04:26:37 Age [y:d:h:m:s]: 02:024:08:12:45
Block: 667165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539075 RingCT/type: yes/0
Extra: 0149d5317f076bcedf577627963342d2b1f5ee5b7741619ea46fa575cc7f5e197b02110000000333af99f4000000000000000000

1 output(s) for total of 3.779247749000 dcy

stealth address amount amount idx
00: 553d30344fa3d271bb5cc34e23806e396192923358f532abe57a147a5761cf93 3.779247749000 1108330 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": 667175, "vin": [ { "gen": { "height": 667165 } } ], "vout": [ { "amount": 3779247749, "target": { "key": "553d30344fa3d271bb5cc34e23806e396192923358f532abe57a147a5761cf93" } } ], "extra": [ 1, 73, 213, 49, 127, 7, 107, 206, 223, 87, 118, 39, 150, 51, 66, 210, 177, 245, 238, 91, 119, 65, 97, 158, 164, 111, 165, 117, 204, 127, 94, 25, 123, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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