Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 211e2a57485f3f95173e8798198d00a074d9739b929d4ecc2756c60e9361a1e9

Tx prefix hash: 72472db1838bca934fb12460ce1475e9409c88ece5babdb1594dd303c9e39ad6
Tx public key: 5175138c83d13036033670933f661c5cbda8c69aa685e5f1a7d083444678be6e
Timestamp: 1705575314 Timestamp [UCT]: 2024-01-18 10:55:14 Age [y:d:h:m:s]: 01:042:09:45:42
Block: 937951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291372 RingCT/type: yes/0
Extra: 015175138c83d13036033670933f661c5cbda8c69aa685e5f1a7d083444678be6e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ffc4ced2ee04bcf3aa1f5ae44b7d8e952fd42e6d32690a28f92384f0c0a730c 0.600000000000 1396015 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": 937961, "vin": [ { "gen": { "height": 937951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ffc4ced2ee04bcf3aa1f5ae44b7d8e952fd42e6d32690a28f92384f0c0a730c" } } ], "extra": [ 1, 81, 117, 19, 140, 131, 209, 48, 54, 3, 54, 112, 147, 63, 102, 28, 92, 189, 168, 198, 154, 166, 133, 229, 241, 167, 208, 131, 68, 70, 120, 190, 110, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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