Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34e6dd8731df9a9f37794a84e68ee666dfa70f699fe9d97c18c99e2e970b1000

Tx prefix hash: 74015bb66052288f3770a084cf786cc96b330190f4a5f3ef406ab4b4f3a251a4
Tx public key: f247f217fcf21537aee5847b5d25c480d2979a6b2a280d6cb2220623b40edb36
Timestamp: 1719347306 Timestamp [UCT]: 2024-06-25 20:28:26 Age [y:d:h:m:s]: 00:273:10:56:56
Block: 1052135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195387 RingCT/type: yes/0
Extra: 01f247f217fcf21537aee5847b5d25c480d2979a6b2a280d6cb2220623b40edb36021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2afc2f8341e0f300125a8469baf8e6cb70e576945f0436b93afb9b393fe5f70 0.600000000000 1522456 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": 1052145, "vin": [ { "gen": { "height": 1052135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2afc2f8341e0f300125a8469baf8e6cb70e576945f0436b93afb9b393fe5f70" } } ], "extra": [ 1, 242, 71, 242, 23, 252, 242, 21, 55, 174, 229, 132, 123, 93, 37, 196, 128, 210, 151, 154, 107, 42, 40, 13, 108, 178, 34, 6, 35, 180, 14, 219, 54, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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