Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d5dce6dda26ad6edc3aa0a8826cf6b0457378fdd1b5aa6ceceeb779d190c133

Tx prefix hash: 14db50e46ae89b82880764ca7d957085d7b14ffa5d84d80dbd1502f02df06cf7
Tx public key: 5f80acec2d858d21ae43924d2c8cf164eb422641594c77338d531a9f8c059d9a
Timestamp: 1676579122 Timestamp [UCT]: 2023-02-16 20:25:22 Age [y:d:h:m:s]: 01:276:11:52:14
Block: 698464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458524 RingCT/type: yes/0
Extra: 015f80acec2d858d21ae43924d2c8cf164eb422641594c77338d531a9f8c059d9a02110000000674b6d784000000000000000000

1 output(s) for total of 2.976451000000 dcy

stealth address amount amount idx
00: aee3bdc79dc6c2ee21b8492e21200cb03e3b5fa5317c9d56e778f072ca10ded1 2.976451000000 1141767 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": 698474, "vin": [ { "gen": { "height": 698464 } } ], "vout": [ { "amount": 2976451000, "target": { "key": "aee3bdc79dc6c2ee21b8492e21200cb03e3b5fa5317c9d56e778f072ca10ded1" } } ], "extra": [ 1, 95, 128, 172, 236, 45, 133, 141, 33, 174, 67, 146, 77, 44, 140, 241, 100, 235, 66, 38, 65, 89, 76, 119, 51, 141, 83, 26, 159, 140, 5, 157, 154, 2, 17, 0, 0, 0, 6, 116, 182, 215, 132, 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