Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bee8f332b50df9e250157a6e6774a558c9fe73b47461a7ebe68134d7f76ab86

Tx prefix hash: 9de4fce68a0e38251e4c8b5d45d3dfe23cad07b0a6c2a8ac13df99eaf5c0fbe2
Tx public key: 1dbde4f407dc2c7178407b1be61ade59179d250b3faeb7228f581870c35bc357
Timestamp: 1723021617 Timestamp [UCT]: 2024-08-07 09:06:57 Age [y:d:h:m:s]: 00:077:08:36:17
Block: 1082603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55387 RingCT/type: yes/0
Extra: 011dbde4f407dc2c7178407b1be61ade59179d250b3faeb7228f581870c35bc35702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ba9db1d17bebc444e8428b2164391e2fee4e7f97ee3e08a0e82ea7b51c85b37 0.600000000000 1556432 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": 1082613, "vin": [ { "gen": { "height": 1082603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ba9db1d17bebc444e8428b2164391e2fee4e7f97ee3e08a0e82ea7b51c85b37" } } ], "extra": [ 1, 29, 189, 228, 244, 7, 220, 44, 113, 120, 64, 123, 27, 230, 26, 222, 89, 23, 157, 37, 11, 63, 174, 183, 34, 143, 88, 24, 112, 195, 91, 195, 87, 2, 17, 0, 0, 0, 5, 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