Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 278ca0168a23d086e9520f2c659ebed833ef791ffd9c38a90ce8d9f9f6f4da82

Tx prefix hash: d9519e5f4bf653284c08ba8573c56a6fa5ded842f6c6b2155949fe55252a4542
Tx public key: 71c47be49637780b4830d3ed2f5318d2ddfb69af54d2a024e049ceed75d9f4fd
Timestamp: 1721969630 Timestamp [UCT]: 2024-07-26 04:53:50 Age [y:d:h:m:s]: 00:258:17:37:07
Block: 1073883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184834 RingCT/type: yes/0
Extra: 0171c47be49637780b4830d3ed2f5318d2ddfb69af54d2a024e049ceed75d9f4fd021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c731b8587abb1c9781feee3f02a1380e680d1f3db16c017cc3330b3b340c65 0.600000000000 1546390 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": 1073893, "vin": [ { "gen": { "height": 1073883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c731b8587abb1c9781feee3f02a1380e680d1f3db16c017cc3330b3b340c65" } } ], "extra": [ 1, 113, 196, 123, 228, 150, 55, 120, 11, 72, 48, 211, 237, 47, 83, 24, 210, 221, 251, 105, 175, 84, 210, 160, 36, 224, 73, 206, 237, 117, 217, 244, 253, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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