Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afb5f4999c3cc51e70d80643569ded79af523c3762b9b265ad4d1c0a28fb5b58

Tx prefix hash: 7665a708ff8b589e77f1b9ef96c66a0293857f30ead115eb37d1a144bde1eede
Tx public key: a7edaa91c3f74ccd3169e0f866e20d2bee3797b36fe94925abafe62d850822b8
Timestamp: 1681931202 Timestamp [UCT]: 2023-04-19 19:06:42 Age [y:d:h:m:s]: 01:357:12:28:17
Block: 742189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516800 RingCT/type: yes/0
Extra: 01a7edaa91c3f74ccd3169e0f866e20d2bee3797b36fe94925abafe62d850822b8021100000002faf35c9c000000000000000000

1 output(s) for total of 2.132160828000 dcy

stealth address amount amount idx
00: f1e7a370d6cc3850d8ac13a0b2a8f17a02381d365cafcd7ec7018096254cc7f1 2.132160828000 1189148 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": 742199, "vin": [ { "gen": { "height": 742189 } } ], "vout": [ { "amount": 2132160828, "target": { "key": "f1e7a370d6cc3850d8ac13a0b2a8f17a02381d365cafcd7ec7018096254cc7f1" } } ], "extra": [ 1, 167, 237, 170, 145, 195, 247, 76, 205, 49, 105, 224, 248, 102, 226, 13, 43, 238, 55, 151, 179, 111, 233, 73, 37, 171, 175, 230, 45, 133, 8, 34, 184, 2, 17, 0, 0, 0, 2, 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