Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73b4d165b9c781cc472eb812b969df520669ed354b822d4b2fa284481b8f04b4

Tx prefix hash: 43f6d4d73bb81c98ae972567e3a9ab283acc924f10dc79e1dd7aea299d44b855
Tx public key: 38562764905be872edd45e3797a17e8110e5024c70484336b5352f36e6ef2564
Timestamp: 1722368650 Timestamp [UCT]: 2024-07-30 19:44:10 Age [y:d:h:m:s]: 00:324:23:51:14
Block: 1077186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232064 RingCT/type: yes/0
Extra: 0138562764905be872edd45e3797a17e8110e5024c70484336b5352f36e6ef256402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0926ca2ff9c9b1c024eb183b303a08c7359a1036f93ea45f87182f6d4e4121d5 0.600000000000 1549733 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": 1077196, "vin": [ { "gen": { "height": 1077186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0926ca2ff9c9b1c024eb183b303a08c7359a1036f93ea45f87182f6d4e4121d5" } } ], "extra": [ 1, 56, 86, 39, 100, 144, 91, 232, 114, 237, 212, 94, 55, 151, 161, 126, 129, 16, 229, 2, 76, 112, 72, 67, 54, 181, 53, 47, 54, 230, 239, 37, 100, 2, 17, 0, 0, 0, 1, 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