Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbabdd079ebec3caa640ad23e502cf3c8d3ae41d4d96ee2b9819e0770b628032

Tx prefix hash: 6b3e6ad3a4e6b3105d055bafa559d9d84b281d5badc6d72970393605b1538ced
Tx public key: 8066a1765256f3563716f0afc437ca1b7cbc1f1bc428e55de4c8137601aea4bf
Timestamp: 1723111309 Timestamp [UCT]: 2024-08-08 10:01:49 Age [y:d:h:m:s]: 00:169:03:17:39
Block: 1083356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120954 RingCT/type: yes/0
Extra: 018066a1765256f3563716f0afc437ca1b7cbc1f1bc428e55de4c8137601aea4bf02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e097f334389153cb703020fd0aee77c6e15f744e58dc6b7a038ae22c64d15f 0.600000000000 1557235 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": 1083366, "vin": [ { "gen": { "height": 1083356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e097f334389153cb703020fd0aee77c6e15f744e58dc6b7a038ae22c64d15f" } } ], "extra": [ 1, 128, 102, 161, 118, 82, 86, 243, 86, 55, 22, 240, 175, 196, 55, 202, 27, 124, 188, 31, 27, 196, 40, 229, 93, 228, 200, 19, 118, 1, 174, 164, 191, 2, 17, 0, 0, 0, 16, 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