Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee6d059d7623afc93e23b2bbb6af3587041ce67fdbb91c613b946e20a905df3

Tx prefix hash: dd70ea4e3bc088250ba5a204ad2acad91ebbf9c744ac7fb587859ddf7fe3a951
Tx public key: f1b0106d739d42fd09251f840bb06ad7a1fffed1b4f87aaaacfdf906255b7f89
Timestamp: 1708900981 Timestamp [UCT]: 2024-02-25 22:43:01 Age [y:d:h:m:s]: 01:066:17:13:25
Block: 965548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308705 RingCT/type: yes/0
Extra: 01f1b0106d739d42fd09251f840bb06ad7a1fffed1b4f87aaaacfdf906255b7f890211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93643ebd391e19b868d47e4a5f7e260fd8643571fb1db75189ab72a11500d5f3 0.600000000000 1425301 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": 965558, "vin": [ { "gen": { "height": 965548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93643ebd391e19b868d47e4a5f7e260fd8643571fb1db75189ab72a11500d5f3" } } ], "extra": [ 1, 241, 176, 16, 109, 115, 157, 66, 253, 9, 37, 31, 132, 11, 176, 106, 215, 161, 255, 254, 209, 180, 248, 122, 170, 172, 253, 249, 6, 37, 91, 127, 137, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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