Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aac43dd5d9992ef4b831e8ec080ac5719c9d3d274d7c029feffc99d97cfd44a4

Tx prefix hash: f4aec4118011cce403fad653e8869dd65288b3692a0573e66b9f04a67a10ed36
Tx public key: b552a8b22fb97d61f5658ae072017392537bbd1e37ede06a7aa7c9a5e07ff12e
Timestamp: 1725323085 Timestamp [UCT]: 2024-09-03 00:24:45 Age [y:d:h:m:s]: 00:256:06:12:31
Block: 1101687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183018 RingCT/type: yes/0
Extra: 01b552a8b22fb97d61f5658ae072017392537bbd1e37ede06a7aa7c9a5e07ff12e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d58574b74519700e2c66fd07b5a169336be1e74edb8f6295624b15a542fd269 0.600000000000 1577830 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": 1101697, "vin": [ { "gen": { "height": 1101687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d58574b74519700e2c66fd07b5a169336be1e74edb8f6295624b15a542fd269" } } ], "extra": [ 1, 181, 82, 168, 178, 47, 185, 125, 97, 245, 101, 138, 224, 114, 1, 115, 146, 83, 123, 189, 30, 55, 237, 224, 106, 122, 167, 201, 165, 224, 127, 241, 46, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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