Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cf8e3eaff3aca5877c3166da4a933bc70937404342e6d2720e346e2b3e16ec

Tx prefix hash: 3b06dde8f80af31ba019e96eb8708ab062106293889642b27c8116de7a9194a9
Tx public key: 2d324ff078d7264c934da4a24b89f910ca5dbc5a19917934f089cf007c96aa5a
Timestamp: 1724276130 Timestamp [UCT]: 2024-08-21 21:35:30 Age [y:d:h:m:s]: 00:239:15:25:28
Block: 1093013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171145 RingCT/type: yes/0
Extra: 012d324ff078d7264c934da4a24b89f910ca5dbc5a19917934f089cf007c96aa5a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6d43c3a30bdd25c12d93b3c38f433c4fc847a338aa744c22e53a7f865c0b72b 0.600000000000 1567872 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": 1093023, "vin": [ { "gen": { "height": 1093013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6d43c3a30bdd25c12d93b3c38f433c4fc847a338aa744c22e53a7f865c0b72b" } } ], "extra": [ 1, 45, 50, 79, 240, 120, 215, 38, 76, 147, 77, 164, 162, 75, 137, 249, 16, 202, 93, 188, 90, 25, 145, 121, 52, 240, 137, 207, 0, 124, 150, 170, 90, 2, 17, 0, 0, 0, 2, 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