Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 165bdf1930978e4f5f09fad949b16c080a2c539fb4124328810ca72563bc0ee9

Tx prefix hash: 099b74eea7aff470c0935ba80cae4898064ed266635e760c71488fab63c32fd6
Tx public key: 803a1513dc1c7a15364c5a1005eb73d3fa776a7733557ae2d93911c58adaf6b4
Timestamp: 1728197804 Timestamp [UCT]: 2024-10-06 06:56:44 Age [y:d:h:m:s]: 01:046:05:31:53
Block: 1125526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291417 RingCT/type: yes/0
Extra: 01803a1513dc1c7a15364c5a1005eb73d3fa776a7733557ae2d93911c58adaf6b402110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eb463a4d8f16a908c4e646f7e4a7f9a9ec38acb230ecde61d5fad99d3ff91ff 0.600000000000 1608277 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": 1125536, "vin": [ { "gen": { "height": 1125526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eb463a4d8f16a908c4e646f7e4a7f9a9ec38acb230ecde61d5fad99d3ff91ff" } } ], "extra": [ 1, 128, 58, 21, 19, 220, 28, 122, 21, 54, 76, 90, 16, 5, 235, 115, 211, 250, 119, 106, 119, 51, 85, 122, 226, 217, 57, 17, 197, 138, 218, 246, 180, 2, 17, 0, 0, 0, 11, 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