Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8498a6fc7aafbf4f7ca33deedb7241d60b05a4026417c8c430aaf18d0bfc33f2

Tx prefix hash: 8285eea09dd2f047e7d1b8f6bf81e1bb8be286322b9e830af716eabe9997e664
Tx public key: fc7e8dba0f6d196965a52257045705803337bf5b63bb8525af7a5d5e11795140
Timestamp: 1700780935 Timestamp [UCT]: 2023-11-23 23:08:55 Age [y:d:h:m:s]: 01:182:13:35:43
Block: 898212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391698 RingCT/type: yes/0
Extra: 01fc7e8dba0f6d196965a52257045705803337bf5b63bb8525af7a5d5e1179514002110000000833af99f4000000000000000000

1 output(s) for total of 0.648441583000 dcy

stealth address amount amount idx
00: 4deb610fdc2cddee550fbd417af061356614d4eb68e53e72d0368e1de0616a5f 0.648441583000 1354619 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": 898222, "vin": [ { "gen": { "height": 898212 } } ], "vout": [ { "amount": 648441583, "target": { "key": "4deb610fdc2cddee550fbd417af061356614d4eb68e53e72d0368e1de0616a5f" } } ], "extra": [ 1, 252, 126, 141, 186, 15, 109, 25, 105, 101, 165, 34, 87, 4, 87, 5, 128, 51, 55, 191, 91, 99, 187, 133, 37, 175, 122, 93, 94, 17, 121, 81, 64, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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