Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c15b624a3b56dc04b0bb569e978e32b76c28d9aa0b39e749f7fa742a57d6bf3

Tx prefix hash: 7b6b1bb7d6abaf83aa90bf5b2708112d40d5e4c771d4f577d99839b23b13ad1a
Tx public key: 85a15c8b8864caca71ee2e3ce36d84c39738dc0c354dd59a7cb53b57504281d3
Timestamp: 1735294982 Timestamp [UCT]: 2024-12-27 10:23:02 Age [y:d:h:m:s]: 00:128:22:54:50
Block: 1184225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91981 RingCT/type: yes/0
Extra: 0185a15c8b8864caca71ee2e3ce36d84c39738dc0c354dd59a7cb53b57504281d3021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 889dda4d7bfe8400fcc7e3bf98ef74ca3a9e058e94de3c350ab1ab1bf62728c8 0.600000000000 1670680 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": 1184235, "vin": [ { "gen": { "height": 1184225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "889dda4d7bfe8400fcc7e3bf98ef74ca3a9e058e94de3c350ab1ab1bf62728c8" } } ], "extra": [ 1, 133, 161, 92, 139, 136, 100, 202, 202, 113, 238, 46, 60, 227, 109, 132, 195, 151, 56, 220, 12, 53, 77, 213, 154, 124, 181, 59, 87, 80, 66, 129, 211, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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