Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fee08e868018c08e54df91fe2d7b1b12b3d32cb9b37e96ca63a3364e2ee28d7e

Tx prefix hash: 095dbd0e05a24f2cc61f408070ea47f801112cb5adbbcf1d6e19955f9d018b7c
Tx public key: 7581c8c2014e7c3624abf84c5e1d9c1d306a3c8c5da92fac42050c76c18049f8
Timestamp: 1699679732 Timestamp [UCT]: 2023-11-11 05:15:32 Age [y:d:h:m:s]: 01:146:08:22:14
Block: 889091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365779 RingCT/type: yes/0
Extra: 017581c8c2014e7c3624abf84c5e1d9c1d306a3c8c5da92fac42050c76c18049f8021100000001faf35c9c000000000000000000

1 output(s) for total of 0.695140252000 dcy

stealth address amount amount idx
00: a8c84352ce2aa1c7fde2993bfed7802d9900701d310074b34fe0fe8834f0c231 0.695140252000 1345068 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": 889101, "vin": [ { "gen": { "height": 889091 } } ], "vout": [ { "amount": 695140252, "target": { "key": "a8c84352ce2aa1c7fde2993bfed7802d9900701d310074b34fe0fe8834f0c231" } } ], "extra": [ 1, 117, 129, 200, 194, 1, 78, 124, 54, 36, 171, 248, 76, 94, 29, 156, 29, 48, 106, 60, 140, 93, 169, 47, 172, 66, 5, 12, 118, 193, 128, 73, 248, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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