Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18aa7941d18d29aa5ee8fb4f55b83605e2247d19571b9bd004f1da1e365040a0

Tx prefix hash: 8130f9029277e5eff83b6588a2d267af3915dc189ae6986701cb39ce1f98722f
Tx public key: 6d244352e74d1f5efefbebfe4a172e5c2a120026fd3693214a1b31a4763d1e8d
Timestamp: 1726092017 Timestamp [UCT]: 2024-09-11 22:00:17 Age [y:d:h:m:s]: 00:165:01:10:38
Block: 1108060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117758 RingCT/type: yes/0
Extra: 016d244352e74d1f5efefbebfe4a172e5c2a120026fd3693214a1b31a4763d1e8d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af739249d6119470b50b28ec2ebd68053937466d5eba0c5f06d01dcb83708f64 0.600000000000 1585821 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": 1108070, "vin": [ { "gen": { "height": 1108060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af739249d6119470b50b28ec2ebd68053937466d5eba0c5f06d01dcb83708f64" } } ], "extra": [ 1, 109, 36, 67, 82, 231, 77, 31, 94, 254, 251, 235, 254, 74, 23, 46, 92, 42, 18, 0, 38, 253, 54, 147, 33, 74, 27, 49, 164, 118, 61, 30, 141, 2, 17, 0, 0, 0, 3, 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