Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aff7d755eda8756241b78a8e5f51a5b0ef709d5e60f72f4977e3d5d6508d260e

Tx prefix hash: 0a7ace68d6d652cfc47143ed5404debd608c538c54eb2989bc7889117db429ae
Tx public key: 0a196fcffc6bbf7bf1602d0b50d1b90f8a1a5386020a170e07f6ac9019cf9288
Timestamp: 1673037166 Timestamp [UCT]: 2023-01-06 20:32:46 Age [y:d:h:m:s]: 02:007:01:37:35
Block: 669070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526954 RingCT/type: yes/0
Extra: 010a196fcffc6bbf7bf1602d0b50d1b90f8a1a5386020a170e07f6ac9019cf928802110000000252542ceb000000000000000000

1 output(s) for total of 3.724717200000 dcy

stealth address amount amount idx
00: 415721c27b9f061b2d5cca6b68648217c4be17d3e3bebf05758cde79567601c1 3.724717200000 1110357 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": 669080, "vin": [ { "gen": { "height": 669070 } } ], "vout": [ { "amount": 3724717200, "target": { "key": "415721c27b9f061b2d5cca6b68648217c4be17d3e3bebf05758cde79567601c1" } } ], "extra": [ 1, 10, 25, 111, 207, 252, 107, 191, 123, 241, 96, 45, 11, 80, 209, 185, 15, 138, 26, 83, 134, 2, 10, 23, 14, 7, 246, 172, 144, 25, 207, 146, 136, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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