Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f5e05c3a4e38e6eb0c8815634ab820ddfb5f7893a0c39e51c9b76f96b5b6780

Tx prefix hash: df1829cb5828012822b2a308a59f84c9cfdcd3f8e63821648c5a5df79598877e
Tx public key: eece0bf5e904083f88623aa0b58191d210e59373560c5ed806204e9ed324b74a
Timestamp: 1715694326 Timestamp [UCT]: 2024-05-14 13:45:26 Age [y:d:h:m:s]: 00:363:21:40:40
Block: 1021867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260125 RingCT/type: yes/0
Extra: 01eece0bf5e904083f88623aa0b58191d210e59373560c5ed806204e9ed324b74a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a8d68df4ff0b4cf5e0d5e5d1e5ca1e0d6b6b28f66a0aaf5645ed75fd8eb7843 0.600000000000 1486302 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": 1021877, "vin": [ { "gen": { "height": 1021867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a8d68df4ff0b4cf5e0d5e5d1e5ca1e0d6b6b28f66a0aaf5645ed75fd8eb7843" } } ], "extra": [ 1, 238, 206, 11, 245, 233, 4, 8, 63, 136, 98, 58, 160, 181, 129, 145, 210, 16, 229, 147, 115, 86, 12, 94, 216, 6, 32, 78, 158, 211, 36, 183, 74, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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