Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9520037d820620fad857e5b15aa4fcc0da875132ea538c68ee2615d93ebeaa0d

Tx prefix hash: 1a6bf4f13e993eabce5d542fc5472fb69a8e0222b086e9366ac835d536ab777d
Tx public key: 0fa9b782ea2eaec249dfe2480f1cd7b2483e3dd19f9fee368d0ed03f20a3062c
Timestamp: 1722544520 Timestamp [UCT]: 2024-08-01 20:35:20 Age [y:d:h:m:s]: 00:227:14:25:27
Block: 1078644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162585 RingCT/type: yes/0
Extra: 010fa9b782ea2eaec249dfe2480f1cd7b2483e3dd19f9fee368d0ed03f20a3062c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e2628a9cbeb55172267262163b42746db369e54a25c5ecded16c15a029a3851 0.600000000000 1551261 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": 1078654, "vin": [ { "gen": { "height": 1078644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e2628a9cbeb55172267262163b42746db369e54a25c5ecded16c15a029a3851" } } ], "extra": [ 1, 15, 169, 183, 130, 234, 46, 174, 194, 73, 223, 226, 72, 15, 28, 215, 178, 72, 62, 61, 209, 159, 159, 238, 54, 141, 14, 208, 63, 32, 163, 6, 44, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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