Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e57ae6ed71a4175457654185650cc232ee0fd26577d573474f4b07883a6442b

Tx prefix hash: f7dc7b35b64b795a28c19b2d6be141dd812bcc0ee2265d33c3515495a08c2c5b
Tx public key: d6c0af42f5ea0be01e1008ed87faf82e1469bf58bd707b0a1cefa92786bf4280
Timestamp: 1695490869 Timestamp [UCT]: 2023-09-23 17:41:09 Age [y:d:h:m:s]: 01:115:18:18:42
Block: 854557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344027 RingCT/type: yes/0
Extra: 01d6c0af42f5ea0be01e1008ed87faf82e1469bf58bd707b0a1cefa92786bf4280021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.904686200000 dcy

stealth address amount amount idx
00: f33210d6b5e17f149833ca6478c3670449276cfa22b219d52e4d9358b6f150ed 0.904686200000 1308539 of 0

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": 854567, "vin": [ { "gen": { "height": 854557 } } ], "vout": [ { "amount": 904686200, "target": { "key": "f33210d6b5e17f149833ca6478c3670449276cfa22b219d52e4d9358b6f150ed" } } ], "extra": [ 1, 214, 192, 175, 66, 245, 234, 11, 224, 30, 16, 8, 237, 135, 250, 248, 46, 20, 105, 191, 88, 189, 112, 123, 10, 28, 239, 169, 39, 134, 191, 66, 128, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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