Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf357bf5d5f1c0a0df64248eb0c3e2e12dfb13465af3ad27c3d3f292dd232c64

Tx prefix hash: af310258120ac427f28b4bba327dbbf0d1cd16a8d02532a3330d05817020b639
Tx public key: baa2925807f26095ab580945aee92b5c3384d10d39d79bfd78f5d223e909418a
Timestamp: 1729582100 Timestamp [UCT]: 2024-10-22 07:28:20 Age [y:d:h:m:s]: 00:037:03:43:52
Block: 1136958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26549 RingCT/type: yes/0
Extra: 01baa2925807f26095ab580945aee92b5c3384d10d39d79bfd78f5d223e909418a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d5d16f378d168011802db5ae8ba4498a719f1943ac24eb6b7a2508aacfd1a3a 0.600000000000 1620361 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": 1136968, "vin": [ { "gen": { "height": 1136958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d5d16f378d168011802db5ae8ba4498a719f1943ac24eb6b7a2508aacfd1a3a" } } ], "extra": [ 1, 186, 162, 146, 88, 7, 242, 96, 149, 171, 88, 9, 69, 174, 233, 43, 92, 51, 132, 209, 13, 57, 215, 155, 253, 120, 245, 210, 35, 233, 9, 65, 138, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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