Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76ec775bcb87916e531058b613f13b5e794ad27b46f3346ae5f354152d7e37ad

Tx prefix hash: a30fb3402e038e9a786c74fa5cf45475fa4523cc4b4d330e342f9f3bddc24348
Tx public key: 3cb5474be89e1b1b2a938e9688f84a69b65799a69c7aaa073b51d08478643919
Timestamp: 1703926197 Timestamp [UCT]: 2023-12-30 08:49:57 Age [y:d:h:m:s]: 01:159:23:29:01
Block: 924294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375494 RingCT/type: yes/0
Extra: 013cb5474be89e1b1b2a938e9688f84a69b65799a69c7aaa073b51d08478643919021100000026e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44612f92d929a1af3bbca38b61d99b3608bc272f1c4f8e7b66d9336ec7a67c91 0.600000000000 1382038 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": 924304, "vin": [ { "gen": { "height": 924294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44612f92d929a1af3bbca38b61d99b3608bc272f1c4f8e7b66d9336ec7a67c91" } } ], "extra": [ 1, 60, 181, 71, 75, 232, 158, 27, 27, 42, 147, 142, 150, 136, 248, 74, 105, 182, 87, 153, 166, 156, 122, 170, 7, 59, 81, 208, 132, 120, 100, 57, 25, 2, 17, 0, 0, 0, 38, 228, 187, 107, 131, 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