Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97bde6f89bdf4bf2f72108f8d7035a0e36d9600a7c4ebe03bd244bd71dbf1a1f

Tx prefix hash: 04f5e109fe367f22a71a44777ad2dddff92a5257c65f7a9613b84014ce49b052
Tx public key: 2036dd89a1c4940c8208b54525a2ab1a9ab6a375f1064ccf4603b0add311736b
Timestamp: 1724179687 Timestamp [UCT]: 2024-08-20 18:48:07 Age [y:d:h:m:s]: 00:247:02:07:39
Block: 1092215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176469 RingCT/type: yes/0
Extra: 012036dd89a1c4940c8208b54525a2ab1a9ab6a375f1064ccf4603b0add311736b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d5aeea09360e0809b5178ad248599475a0f31522d60a2ff5e4186d11b2f559f 0.600000000000 1566918 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": 1092225, "vin": [ { "gen": { "height": 1092215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d5aeea09360e0809b5178ad248599475a0f31522d60a2ff5e4186d11b2f559f" } } ], "extra": [ 1, 32, 54, 221, 137, 161, 196, 148, 12, 130, 8, 181, 69, 37, 162, 171, 26, 154, 182, 163, 117, 241, 6, 76, 207, 70, 3, 176, 173, 211, 17, 115, 107, 2, 17, 0, 0, 0, 2, 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