Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da8398a32fc7f370efccda397b21a3c5852f5c78b15904841cf4764741fb3ce

Tx prefix hash: 4a557ff1c7709d024d9548b27e584a9dd7dd69996e7f8150dba9c9e62c0ef570
Tx public key: 8659cfbf1a5d081e0d3b89c0df3a3ff8d834183ee0243fdcd2888f5cde2fa5bf
Timestamp: 1639027648 Timestamp [UCT]: 2021-12-09 05:27:28 Age [y:d:h:m:s]: 02:351:19:11:53
Block: 391568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769484 RingCT/type: yes/0
Extra: 018659cfbf1a5d081e0d3b89c0df3a3ff8d834183ee0243fdcd2888f5cde2fa5bf021100000018379224c2000000000000000000

1 output(s) for total of 30.943756305000 dcy

stealth address amount amount idx
00: 74a62394abf1b34db0f986a77775feb21fdc562db61bd93deabd3eb17bf6b15b 30.943756305000 787997 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": 391578, "vin": [ { "gen": { "height": 391568 } } ], "vout": [ { "amount": 30943756305, "target": { "key": "74a62394abf1b34db0f986a77775feb21fdc562db61bd93deabd3eb17bf6b15b" } } ], "extra": [ 1, 134, 89, 207, 191, 26, 93, 8, 30, 13, 59, 137, 192, 223, 58, 63, 248, 216, 52, 24, 62, 224, 36, 63, 220, 210, 136, 143, 92, 222, 47, 165, 191, 2, 17, 0, 0, 0, 24, 55, 146, 36, 194, 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