Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e365a594e8512123237ef45f5801e27f0708d11c28327f1a03447310648d6e

Tx prefix hash: b4cb44d77ab100e74c485a76d44ddbf291b208462098bd333fddb68cffe8ef52
Tx public key: eadb6ea7a895aa4c0b46e10d439f5326fa85ff9a84469768c65642d875e22a2c
Timestamp: 1716138092 Timestamp [UCT]: 2024-05-19 17:01:32 Age [y:d:h:m:s]: 00:231:15:46:11
Block: 1025537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165817 RingCT/type: yes/0
Extra: 01eadb6ea7a895aa4c0b46e10d439f5326fa85ff9a84469768c65642d875e22a2c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d75eba961b1cf4c314f60a95f26f0d79edb108edb1364f4df3f5489013b0e845 0.600000000000 1492116 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": 1025547, "vin": [ { "gen": { "height": 1025537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d75eba961b1cf4c314f60a95f26f0d79edb108edb1364f4df3f5489013b0e845" } } ], "extra": [ 1, 234, 219, 110, 167, 168, 149, 170, 76, 11, 70, 225, 13, 67, 159, 83, 38, 250, 133, 255, 154, 132, 70, 151, 104, 198, 86, 66, 216, 117, 226, 42, 44, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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