Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 715f6cfd031409be9f382ea23e231e6dc9dba8daa2a727490b0966d2005d0dd0

Tx prefix hash: 094f6050a73cca44db0fba698dbd93cd076bf2bb6e20a3ebdb2d1624eeb49c22
Tx public key: 9b82e821b5fa8a49bda61d0fa48d32bd80275503e557d44102df7f13fb92ccec
Timestamp: 1712387959 Timestamp [UCT]: 2024-04-06 07:19:19 Age [y:d:h:m:s]: 01:277:03:40:55
Block: 994419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456868 RingCT/type: yes/0
Extra: 019b82e821b5fa8a49bda61d0fa48d32bd80275503e557d44102df7f13fb92ccec02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18fa42eb74df7adfc78dac6b8d24a963be2751c35a0c6d37bd5285e092783186 0.600000000000 1454821 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": 994429, "vin": [ { "gen": { "height": 994419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18fa42eb74df7adfc78dac6b8d24a963be2751c35a0c6d37bd5285e092783186" } } ], "extra": [ 1, 155, 130, 232, 33, 181, 250, 138, 73, 189, 166, 29, 15, 164, 141, 50, 189, 128, 39, 85, 3, 229, 87, 212, 65, 2, 223, 127, 19, 251, 146, 204, 236, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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