Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7ae535bd76a965c59990344e2de9b55089b5b90179ef6ecbdbacea889e99165

Tx prefix hash: ffaee691db22911e9011f5e9d3d8493a2bfa1d3a0f4c6c1c0658718ed9356ac3
Tx public key: 7fa89135f9b33cfc2a6985ca5f069aa4c5281ea6f670474b30de1c92c313e30d
Timestamp: 1726369095 Timestamp [UCT]: 2024-09-15 02:58:15 Age [y:d:h:m:s]: 00:074:08:35:32
Block: 1110354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53171 RingCT/type: yes/0
Extra: 017fa89135f9b33cfc2a6985ca5f069aa4c5281ea6f670474b30de1c92c313e30d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ffb6019633fc4f979cb0d4400a9f0eb870a6526f516a11bccd1061835f9736a 0.600000000000 1588929 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": 1110364, "vin": [ { "gen": { "height": 1110354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ffb6019633fc4f979cb0d4400a9f0eb870a6526f516a11bccd1061835f9736a" } } ], "extra": [ 1, 127, 168, 145, 53, 249, 179, 60, 252, 42, 105, 133, 202, 95, 6, 154, 164, 197, 40, 30, 166, 246, 112, 71, 75, 48, 222, 28, 146, 195, 19, 227, 13, 2, 17, 0, 0, 0, 6, 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