Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15a035d8022da56049f5603833bcf3234fc34d6c5e43cf405d43a83f4ade4a3f

Tx prefix hash: d3b618bd8f609eaf201de34fad91260027bffe320b1444d0f9c1f83cb7a7b46b
Tx public key: fafcc1f9d4f1c7869c149e320f71f97773c4a2165d8256ab443647db06c3ae36
Timestamp: 1724957272 Timestamp [UCT]: 2024-08-29 18:47:52 Age [y:d:h:m:s]: 00:258:09:32:19
Block: 1098651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184558 RingCT/type: yes/0
Extra: 01fafcc1f9d4f1c7869c149e320f71f97773c4a2165d8256ab443647db06c3ae36021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65cf093f74af5062334c9de9c2d5a1e7af517e83f531ce26dfada40b60b7779b 0.600000000000 1574440 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": 1098661, "vin": [ { "gen": { "height": 1098651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65cf093f74af5062334c9de9c2d5a1e7af517e83f531ce26dfada40b60b7779b" } } ], "extra": [ 1, 250, 252, 193, 249, 212, 241, 199, 134, 156, 20, 158, 50, 15, 113, 249, 119, 115, 196, 162, 22, 93, 130, 86, 171, 68, 54, 71, 219, 6, 195, 174, 54, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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