Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa37a38fbe76113bbf6fcb4155fb1f2b3f7ba4ee904a9459f43ea0b8ee7bf5e0

Tx prefix hash: 26e10e86fb4c4db3272fb7d7186e9be4521057a97d66fd2ab7d70e8d46fc1dfe
Tx public key: 48e8cd58fd4dba6fdfdf7a0b00d2c16bbc2020ec8ab99b98b6a28a9d2676b1b4
Timestamp: 1723395977 Timestamp [UCT]: 2024-08-11 17:06:17 Age [y:d:h:m:s]: 00:286:05:54:11
Block: 1085711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204496 RingCT/type: yes/0
Extra: 0148e8cd58fd4dba6fdfdf7a0b00d2c16bbc2020ec8ab99b98b6a28a9d2676b1b4021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e25a7d8e63962282df576fd6f29c5c8348642f3c256aa03f75af16feaf704624 0.600000000000 1560300 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": 1085721, "vin": [ { "gen": { "height": 1085711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e25a7d8e63962282df576fd6f29c5c8348642f3c256aa03f75af16feaf704624" } } ], "extra": [ 1, 72, 232, 205, 88, 253, 77, 186, 111, 223, 223, 122, 11, 0, 210, 193, 107, 188, 32, 32, 236, 138, 185, 155, 152, 182, 162, 138, 157, 38, 118, 177, 180, 2, 17, 0, 0, 0, 7, 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