Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18732ab6b38ba118f3c7eb1dc4f9f1cc5b44cc24f3d84aa02f47dd85408940b6

Tx prefix hash: 157fc72f4947d4e5c1114788f08c78ddad47bdb56a34ddc70f2e435ca48f0076
Tx public key: 4a2afd91a49c0f31f8c7f54927eea00a57bd9dc936348f6efe45708029c1b33b
Timestamp: 1696945717 Timestamp [UCT]: 2023-10-10 13:48:37 Age [y:d:h:m:s]: 01:178:09:08:52
Block: 866637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388511 RingCT/type: yes/0
Extra: 014a2afd91a49c0f31f8c7f54927eea00a57bd9dc936348f6efe45708029c1b33b021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.825034089000 dcy

stealth address amount amount idx
00: 01e8cb5e9d4dfb943da2afe9785e97d203e73dbd84b2c895ec557eb79bd03d0e 0.825034089000 1321251 of 0

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": 866647, "vin": [ { "gen": { "height": 866637 } } ], "vout": [ { "amount": 825034089, "target": { "key": "01e8cb5e9d4dfb943da2afe9785e97d203e73dbd84b2c895ec557eb79bd03d0e" } } ], "extra": [ 1, 74, 42, 253, 145, 164, 156, 15, 49, 248, 199, 245, 73, 39, 238, 160, 10, 87, 189, 157, 201, 54, 52, 143, 110, 254, 69, 112, 128, 41, 193, 179, 59, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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