Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51c7a098b990b9b1f6c1df41876e7bccd46b520ab51ac866a50ccfd163999fae

Tx prefix hash: ec689f24fe59104dd824484d4c8afbbd1b9de44891e540dc6df7394232ffbae1
Tx public key: bd8fabcee379cb62fafad9f68ab0c947a99538951f639b58d6cd1500d67de456
Timestamp: 1698157092 Timestamp [UCT]: 2023-10-24 14:18:12 Age [y:d:h:m:s]: 01:129:05:08:06
Block: 876676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353328 RingCT/type: yes/0
Extra: 01bd8fabcee379cb62fafad9f68ab0c947a99538951f639b58d6cd1500d67de45602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.764202588000 dcy

stealth address amount amount idx
00: 4b1b69d1d87382fa5eb9314fc25d31d326223cc2811df4af82dc947ec2cd8ee3 0.764202588000 1332016 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": 876686, "vin": [ { "gen": { "height": 876676 } } ], "vout": [ { "amount": 764202588, "target": { "key": "4b1b69d1d87382fa5eb9314fc25d31d326223cc2811df4af82dc947ec2cd8ee3" } } ], "extra": [ 1, 189, 143, 171, 206, 227, 121, 203, 98, 250, 250, 217, 246, 138, 176, 201, 71, 169, 149, 56, 149, 31, 99, 155, 88, 214, 205, 21, 0, 214, 125, 228, 86, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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