Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ccf98daf975000129627875fd5babb62f928f760414b2bda378d7b484c185e9

Tx prefix hash: b5c16a6b537e64e551a9e677e090c005d6d6f6d102e28c7f41a7ec749252e3d3
Tx public key: 55a132ce4be850546ca6fafd42cf63bdc6fcf17f9c40dbe63d307cd7527240c1
Timestamp: 1581463020 Timestamp [UCT]: 2020-02-11 23:17:00 Age [y:d:h:m:s]: 04:317:03:47:49
Block: 62997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118885 RingCT/type: yes/0
Extra: 0155a132ce4be850546ca6fafd42cf63bdc6fcf17f9c40dbe63d307cd7527240c1021100000015d81c26c0000000000000000000

1 output(s) for total of 379.547033733000 dcy

stealth address amount amount idx
00: 13c2c6771ca4ab6503c160b829d05d5c9d3f7faf141763624ad9632c379a0da3 379.547033733000 116178 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": 63007, "vin": [ { "gen": { "height": 62997 } } ], "vout": [ { "amount": 379547033733, "target": { "key": "13c2c6771ca4ab6503c160b829d05d5c9d3f7faf141763624ad9632c379a0da3" } } ], "extra": [ 1, 85, 161, 50, 206, 75, 232, 80, 84, 108, 166, 250, 253, 66, 207, 99, 189, 198, 252, 241, 127, 156, 64, 219, 230, 61, 48, 124, 215, 82, 114, 64, 193, 2, 17, 0, 0, 0, 21, 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