Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 137ca20d6bae9dedf708f61a5874ca43a15aebb7772ea1abc26c225d48852d30

Tx prefix hash: 0c2549fc74fb6fa70d28a2ea069c24a3ec248c42d0b18c912ce145f1fdc29578
Tx public key: f5498216430db9fdd3411cdf09033baa96e965053842b79a849f2c3fd625d6cd
Timestamp: 1578478348 Timestamp [UCT]: 2020-01-08 10:12:28 Age [y:d:h:m:s]: 05:062:03:58:00
Block: 41126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194456 RingCT/type: yes/0
Extra: 01f5498216430db9fdd3411cdf09033baa96e965053842b79a849f2c3fd625d6cd02110000000bd81c26c0000000000000000000

1 output(s) for total of 448.469937173000 dcy

stealth address amount amount idx
00: a3ede6ccf7b709190f5628fc953011e50bdb99e480d880b3d437a1d3c979c3a7 448.469937173000 72956 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": 41136, "vin": [ { "gen": { "height": 41126 } } ], "vout": [ { "amount": 448469937173, "target": { "key": "a3ede6ccf7b709190f5628fc953011e50bdb99e480d880b3d437a1d3c979c3a7" } } ], "extra": [ 1, 245, 73, 130, 22, 67, 13, 185, 253, 211, 65, 28, 223, 9, 3, 59, 170, 150, 233, 101, 5, 56, 66, 183, 154, 132, 159, 44, 63, 214, 37, 214, 205, 2, 17, 0, 0, 0, 11, 216, 28, 38, 192, 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