Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4764b7aee99480d4b6a7b81263373f3558be245da3b5d60e776db09a20352b3

Tx prefix hash: 9056f47e3acae1fff0893710d5a7752b5c10901d4244a38c70d0830c44c18451
Tx public key: 300b31559fc97562528d5614b5a1ea98f12b92267377e14a17dbd51f2558612a
Timestamp: 1700893038 Timestamp [UCT]: 2023-11-25 06:17:18 Age [y:d:h:m:s]: 01:346:19:33:35
Block: 899148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506733 RingCT/type: yes/0
Extra: 01300b31559fc97562528d5614b5a1ea98f12b92267377e14a17dbd51f2558612a0211000000014b8f5122000000000000000000

1 output(s) for total of 0.643797679000 dcy

stealth address amount amount idx
00: dd8c0bc7e8de33e8daefa9d73171c5326cfd49fade4c2d36496983d7f774903e 0.643797679000 1355591 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": 899158, "vin": [ { "gen": { "height": 899148 } } ], "vout": [ { "amount": 643797679, "target": { "key": "dd8c0bc7e8de33e8daefa9d73171c5326cfd49fade4c2d36496983d7f774903e" } } ], "extra": [ 1, 48, 11, 49, 85, 159, 201, 117, 98, 82, 141, 86, 20, 181, 161, 234, 152, 241, 43, 146, 38, 115, 119, 225, 74, 23, 219, 213, 31, 37, 88, 97, 42, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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