Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 891668acf8f3b90ad2f3957d95de9f419c3c9a6a6c7618a7ac62441bd971567a

Tx prefix hash: a693718901dfab8ef956984ce735491c95b8da6527263806a6e0b1666e23a7ac
Tx public key: e95fe56ffbce4b3dc04d0bd7c4a35e708dafe55da365e6410970c4f2bc5b7f61
Timestamp: 1719427155 Timestamp [UCT]: 2024-06-26 18:39:15 Age [y:d:h:m:s]: 01:133:07:24:58
Block: 1052803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353809 RingCT/type: yes/0
Extra: 01e95fe56ffbce4b3dc04d0bd7c4a35e708dafe55da365e6410970c4f2bc5b7f610211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54bfa4f05aa0e24136990e7913444fd7313212577b08e0b96f2eb6b4fed1a521 0.600000000000 1523136 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": 1052813, "vin": [ { "gen": { "height": 1052803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54bfa4f05aa0e24136990e7913444fd7313212577b08e0b96f2eb6b4fed1a521" } } ], "extra": [ 1, 233, 95, 229, 111, 251, 206, 75, 61, 192, 77, 11, 215, 196, 163, 94, 112, 141, 175, 229, 93, 163, 101, 230, 65, 9, 112, 196, 242, 188, 91, 127, 97, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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