Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3b5a352980b3706b17ed6212514bcb4cd1e9d0433c87a3fcca496153ff09f0e

Tx prefix hash: 0c43eed33f0a335b7a2de64d4539ec2401c00adf76de73b12e6540ef445b0c91
Tx public key: 34386b0c207590e9ee7bf9e879ee2a28e090ecc19b421c032a058e262c81e4ae
Timestamp: 1721753793 Timestamp [UCT]: 2024-07-23 16:56:33 Age [y:d:h:m:s]: 00:256:08:51:26
Block: 1072086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183147 RingCT/type: yes/0
Extra: 0134386b0c207590e9ee7bf9e879ee2a28e090ecc19b421c032a058e262c81e4ae02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 350e09ef7231dafc5fd81810aabfe77d7ecc7e568ba4e695572181c0533dd2a8 0.600000000000 1544533 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": 1072096, "vin": [ { "gen": { "height": 1072086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "350e09ef7231dafc5fd81810aabfe77d7ecc7e568ba4e695572181c0533dd2a8" } } ], "extra": [ 1, 52, 56, 107, 12, 32, 117, 144, 233, 238, 123, 249, 232, 121, 238, 42, 40, 224, 144, 236, 193, 155, 66, 28, 3, 42, 5, 142, 38, 44, 129, 228, 174, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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