Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66959930a4fcc9461d79d85f48b15df888b32155e0056c6a82b3f874b4028c1f

Tx prefix hash: 14c8387209019cb54a24e175fb401ca22dd717635b3dfbf39cbf2c46a5231eaa
Tx public key: 1dce876dccc90319e8fb7cdd5f4bb8d784cda8c7f7b2b0179e43c45e4c3814f2
Timestamp: 1574519552 Timestamp [UCT]: 2019-11-23 14:32:32 Age [y:d:h:m:s]: 05:047:09:16:50
Block: 15616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1176883 RingCT/type: yes/0
Extra: 011dce876dccc90319e8fb7cdd5f4bb8d784cda8c7f7b2b0179e43c45e4c3814f2021100000017f95225a5000000000000000000

1 output(s) for total of 544.826963577000 dcy

stealth address amount amount idx
00: 433cfb67ca6f9b375576ed1e77de026a141a960c57b509afa96ea3e86a0219d0 544.826963577000 21065 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": 15626, "vin": [ { "gen": { "height": 15616 } } ], "vout": [ { "amount": 544826963577, "target": { "key": "433cfb67ca6f9b375576ed1e77de026a141a960c57b509afa96ea3e86a0219d0" } } ], "extra": [ 1, 29, 206, 135, 109, 204, 201, 3, 25, 232, 251, 124, 221, 95, 75, 184, 215, 132, 205, 168, 199, 247, 178, 176, 23, 158, 67, 196, 94, 76, 56, 20, 242, 2, 17, 0, 0, 0, 23, 249, 82, 37, 165, 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