Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1891898e6f3c5ed5f3686725b880f0c7828b822c22b34149738ea72c74d24960

Tx prefix hash: 863128cc4ab3a747a91d89411e7b71c189ecb2966059964751b2e9b9d576e6b5
Tx public key: def1a86ef0c6928ce461156f726bc05d28a8da2202e004d0dcc4aa6c61b83f7e
Timestamp: 1580796431 Timestamp [UCT]: 2020-02-04 06:07:11 Age [y:d:h:m:s]: 04:329:05:26:01
Block: 58464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126521 RingCT/type: yes/0
Extra: 01def1a86ef0c6928ce461156f726bc05d28a8da2202e004d0dcc4aa6c61b83f7e021100000158b221b3d1000000000000000000

1 output(s) for total of 392.902976616000 dcy

stealth address amount amount idx
00: 02e112afcfe8854254d08ba0bac43ccae12108c9bc875cbf9397d0312e3749e1 392.902976616000 107998 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": 58474, "vin": [ { "gen": { "height": 58464 } } ], "vout": [ { "amount": 392902976616, "target": { "key": "02e112afcfe8854254d08ba0bac43ccae12108c9bc875cbf9397d0312e3749e1" } } ], "extra": [ 1, 222, 241, 168, 110, 240, 198, 146, 140, 228, 97, 21, 111, 114, 107, 192, 93, 40, 168, 218, 34, 2, 224, 4, 208, 220, 196, 170, 108, 97, 184, 63, 126, 2, 17, 0, 0, 1, 88, 178, 33, 179, 209, 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